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

Run without Nginx #53

Open
Digital39999 opened this issue Oct 11, 2024 · 6 comments
Open

Run without Nginx #53

Digital39999 opened this issue Oct 11, 2024 · 6 comments

Comments

@Digital39999
Copy link

Digital39999 commented Oct 11, 2024

Is there a way to run huly without nginx and let us actually take care of access to it and securing it?
Forcing us to use nginx and even worse if I already have one is really inconvenient.

@jondef
Copy link

jondef commented Oct 11, 2024

You can use traefik is you want or any other reverse proxy

@Digital39999
Copy link
Author

Well is there a way to run it without a proxy at all? Why is proxy needed?

@jondef
Copy link

jondef commented Oct 11, 2024

I don't think running this project without a reverse proxy is a good idea, because it's a microservice architecture- there's like 6 of them or more, and so you need a reverse proxy to forward the incoming requests to the correct container based on the port and url. What's your setup you currently have?

@Digital39999
Copy link
Author

I didn't realize it was actually running multiple different services, I thought it was just a single service that coordinates the endpoints. Makes sense now why it needs to have endpoints rewritten. I was thinking it would be easier to self-host, especially if it's running on a local server under a NAS rather than a public VPS with a dedicated IP.

@ja49619
Copy link
Contributor

ja49619 commented Oct 13, 2024

I didn't realize it was actually running multiple different services, I thought it was just a single service that coordinates the endpoints. Makes sense now why it needs to have endpoints rewritten. I was thinking it would be easier to self-host, especially if it's running on a local server under a NAS rather than a public VPS with a dedicated IP.

no matter where you run on nas or vps. for you as a user there will be only one endpoint - ip:8087.

In general, the question you raised is relevant. There are more convenient and modern reverse proxies, but the automatic installation script imposes the dinosaur nginx. Just give the choice “with or without a proxy”, and then we’ll figure out what to redirect through.

@Digital39999
Copy link
Author

In general, the question you raised is relevant. There are more convenient and modern reverse proxies, but the automatic installation script imposes the dinosaur nginx. Just give the choice “with or without a proxy”, and then we’ll figure out what to redirect through.

You're absolutely right. The only confusion I have is that in the README, it mentions Nginx is running as a service via systemctl, rather than being set up in the Docker Compose file, which would route everything together. I wouldn't want to install anything directly on my system — I prefer to keep everything contained within a single Docker Compose setup or in multiple containers.

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

3 participants