Replies: 3 comments 1 reply
-
It means that the server communicates with anything outside, not the client (e.g. your browser). So API calls to fetch [potentially private] info are made server-side and only the sanitized output is returned. Thats what a proxy is. This has nothing to do with a reverse proxy which is a different (but of course related) concept. |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
homepage.dev was highly recommended on a recent lemmy thread. I was drawn by the idea of having a portal where all of my self-hosted apps could be linked. But when I saw that homepage was 'fully proxied', I hoped that it would eliminate the configuration of nginx to go to all of these apps.
However, I did not find that to be the case.
It seems that homepage still requires the use of a reverse proxy, especially if you want to use https and there doesn't seem to be an obvious setting/configuration to actually proxy traffic sent from
https://localhost/syncthing
(for example) to it's containerhttp://syncthing:8384
.homepage is described as "A modern, fully static, fast, secure fully proxied, highly customizable application dashboard with integrations for over 100 services and translations into multiple languages."
What does this mean?
Beta Was this translation helpful? Give feedback.
All reactions