wger-project
Add documentation and image that does not set up an nginx reverse proxy.
Use case
Hi.
I'd love to be able to run your application, but the production image is tied heavily into the nginx reverse proxy. This is the only selfhosted image I am running with the exception of nextcloud that has this type of setup, and it makes it very difficult for integrating into existing systems, or running these applications side by side for instance.
I have looked at using the development image, but the instructions are tedious and I dislike the large amount of setup required every time the container is restarted, removed, deleted etc... it sort of defeats the idea of using a docker image.
Proposal
Could you please consider making a base image that serves a http page, that has an included postgreSQL or mariadb image, celery etc... or a compose file with a similar base image, and the ability to use our own postgreSQL image etc... with docker volume mounts etc... no need to have to bootstrap the install etc...
This means that for anyone hosting any other services in addition to wger, that they can use their own reverse proxy with letsencrypt certs etc... and have setup complete in 5 minutes or so, and prevent a heap of headaches when troubleshooting.
Thanks for taking the time to read and consider.
Edit: I see that you can just point your existing reverse proxy to the nginx one that is set up. Ideally though not to have multiple reverse proxies running. Thanks for considering.
Edit: Would you also mind adding into documentation that for portainer users that the nginx and redis .conf files must be uploaded as mounts into the compose? Cheers!
Additional Context
No response
Hi! You need a reverse proxy. The reason is that Django doesn't serve any static files during production and needs a different service to do that. You can use your existing nginx without problem, you just need to make sure the static files are server from the correct url, just take a look at our nginx config file
I feel like this issue is relevant for me. I have just started with the docker compose, but I cannot find the right port to use for seeing the nginx served web ui. From the docker compose, I think it's suppose to be localhost:80, but that's already in use on my system(nginx). I've tried changing the host port in the ports section of nginx in the docker compose, it just doesn't work. I feel like this could be simpler if it didn't come with its own nginx, for those that already use it.
Aha, I totally removed the "nginx" section in the docker compose, added "ports" containing my_desired_port:8000 in the "web" section, so that I have control over the host port this is served at. And it works, sort of. I think I can maybe take it from here. My plan is to have my existing nginx proxy manager serve it up in a proxy, as I've done for dozens of other apps. Bummer, I was not able to get it to work after all.
It looks like this PR might help me out... https://github.com/wger-project/docker/issues/138 So Ill just wait and see if/when this is merged.
