Added Dockerfiles #25
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
... not necessary.
- Back-end and front-end are separated - Can still use Docker and also bundle it
ricardobalk
added
hacktoberfest
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added a Docker-setup. The back-end (API) and front-end (map) are separated, but thanks to
docker-compose, required data volumes are created and the stuff is started in the right order.The front-end gets built first, then added to the back-end and after that, the back-end is started.
People can run the back-end, front-end or both, with or without Docker. Docker is recommended, but I still need to write some docs on how to use this set-up.
However, after cloning, setting up the Mapbox access token (in
./web/.env.local), people could just dodocker-compose up. It will do the rest. (Assuming an up-to-date Docker and docker-compose installation.)