-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
YUNOhost integration #11
Comments
Started a support thread for it: https://forum.yunohost.org/t/have-multiple-domains-point-to-the-same-application/29731 |
Okay I think I have a pretty good idea for YNH integration now. There'll be a "main app", the Essy app, that'll provide the management interface, and store the site's data. This app will boot a child nginx proxy that it can manage completely, and its own process. Then there'll be the "Essy Website" sub-app, which does nothing but provide a nginx snippet to catch and redirect to the Essy main instance. I think that for ease of use, I'll disable the adding of domains from within Essy entirely, and instead direct to using that sub-app instead. The sub-app itself will then also assert that it is indeed making that website available, there'll have to be some crimes or cross-app nudging to make this happen, but it can be a thing. So with this, the management of domains and certificates is entirely put on YNH and its support, while Essy can focus on delivering files and the likes to requests on those domains. So the user-side flow would look something like the following;
|
With it being this easy, I actually want to have this for v1, so that it's easily doable and installable. |
I don't know if it's possible, but i'd like to integrate with YUNOhost, make it installable on there, and let it manage domains and websites in that environment.
YUNO manages the "front", so i'd have to figure out if its possible to have it forward domains to some internal context, but thats a problem to figure out.
The text was updated successfully, but these errors were encountered: