Suggestion: Docker enhancements

[allgood]

While trying a better way to deploy the application and generate letsencrypt certificates ( see #534 ) I got on the problem of having two nginx instances and this looks something incorrect.

I'm working on a way to be able to run whaticket on a setup like this:

• nginx-proxy (new)
• acme-companion (optional - only if SSL is used)
• backend (exactly as current)
• frontend (change to a small http server like busybox)
• mysql (exactly as current)

Maybe a phpmyadmin container can be added, possible using the fpm version and tying it to the nginx-proxy.

After all of this I want to be able to publish the containers on docker.io or any other docker registry and start a working setup of Whaticket just with a docker-compose.yml file and some configuration files.

I'm working on this idea and would appreciate any comments on it.

[allgood]

First tests successful, frontend running on busybox httpd server on a very light docker image. In order to serve the index.html to the routed URLs of the frontend I had to set it as the default 404 page, if one analise the communication on the webclient console page it will show that error code but the page keeps working.

Only way to avoid this is using some other webserver, something like lighttpd that have a good support for URL rewriting.

[allgood]

First tests is in a branch of my fork: https://github.com/allgood/whaticket-community/tree/docker-enhancements

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.