![]() This could be handled via requests between yunohost and the proxy service. For example - the default config could be to simply assign each app its own subdomain when it is installed (and do all the various xmpp / mail / etc. With a service like boringproxy (or ngrok) configured to reduce the burden on the yunohost user, you could dramatically reduce the need to understand or configure domains at all. The user still has to configure their DNS in some way / add ports and subdomains for xmpp / etc. So the end user would not have to know what a port even is, much less configure one on their router.ĭNS / domain management. Forward facing proxy services like boringproxy.io or ngrok allow you to map ports on your local server to the reverse proxy entirely through their application, which maintains a tunneling connection with the external reverse proxy. You would need to open 0 ports in the router - in fact you wouldn’t need to do anything at all with the router. Hey SohKa - thanks for diving into this suggestion! I’ll answer point by point. This seems too easy - and would make self-hosting much more availble to the common person, right? Or am I missing something? on the local yunohost, since the service is just in charge of forwarding requests. handled automagically between yunohost and the service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |