-
Notifications
You must be signed in to change notification settings - Fork 210
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 backend and frontend as separate services #118
Comments
Also I already made the changes for mongo+react in a different branch. I can push it if you want to have a look. |
Hi @mehiX. Thank you for the suggestion. Static resources are served by the backend container because there is no server-side rendering in the frontend templates that would require its own server. In the current setup, there isn't much difference in who serves the static content, so I kept it as simple as possible. Why do you need them separated? |
@Shpota I understood you wanted to keep it simple. So you I. However I've never worked on a project (let alone one that runs in production) that mixes fronend and backend in the same container. there are lots of benefits to have them separated. I agree with you that in this setup it doesn't really matter who serves that static content. If the project is not meant to be extended and used in real project, you are right it can stay as it is. |
At the moment both backend and frontend are running in the same container.
It would be great to have them separated. For example,
docker-compose.yml
would look like:Backend and frontend have their own
Dockerfile
and can be built and restarted independently.The text was updated successfully, but these errors were encountered: