I don't want docker (for now) to be used during development, the setup is simple enough and if so you can always use the production version (but not vice-versa, that's the reason)
As we're using docker-compose I change the service / container-names - let docker-compose handle and prefix them
Since publishing a pre-build version to docker-hub I'd be impossible to update the configuration files after pulling the images therefore both the backend and front-end get build every time which allows you to update your configuration every time you start it.
For performance reasons I'd prefer that the frontend get's served directly by the tool of your choice (e.g. nginx, apache etc..). Serving the frontend twice using proxy_pass causes a useless performance overhead.
PS: I don't know what happend but apparently github doesn't display any commits on this branch here...
Related issues / PRs
https://github.com/dot-cafe/beam.cafe/issues/4
Short description and why it's useful
The docker support help the program to be installed more easily and scalable
Short description and why it's useful
I have an issue with the frontend for some reason
![image](https://user-images.githubusercontent.com/13888068/86957948-717c1a80-c129-11ea-915a-bd54e4b1700a.png)