Skip to content
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

Open
ShadowJonathan opened this issue May 22, 2024 · 3 comments
Open

YUNOhost integration #11

ShadowJonathan opened this issue May 22, 2024 · 3 comments
Milestone

Comments

@ShadowJonathan
Copy link
Owner

ShadowJonathan commented May 22, 2024

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.

@ShadowJonathan ShadowJonathan added this to the Misc (1.x) milestone May 22, 2024
@ShadowJonathan
Copy link
Owner Author

@ShadowJonathan
Copy link
Owner Author

ShadowJonathan commented May 24, 2024

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;

  • You install the main Essy app, and set it up.
  • For every domain you want to manage via Essy, you install an "Essy Domain" app, and that domain will appear within the Essy management interface.
  • You use the Essy app to configure files for those domains, and edit them from there.

@ShadowJonathan
Copy link
Owner Author

With it being this easy, I actually want to have this for v1, so that it's easily doable and installable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant