Docker compose support #54
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
sissbruecker
reviewed
Jan 1, 2021
|
@LivingWithHippos Looks good, thanks for your contribution! Looking at the headlines in the README it probably makes sense to restructure them a little bit, but I can take care of that later on. |
|
@LivingWithHippos Perfect, thanks again! |
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.
Added the docker-compose.yml file and some instructions. I wasn't sure about how much text needed to be repeated.
docker-compose exec linkding python manage.py createsuperuser --username=joe --email=joe@example.comallows people to run this command even if they changed the container name sincedocker-compose execchecks for the service name indocker-compose.ymland not the container name.Tested with and without the
.envfile