feat: complete docker release ver init #194
Merged
Conversation
This file contains hidden or 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
Because create a new problem with web after start services is complex, I build a new problem file and write the scripts to finish it.
In this commit we have three side: 1. Use Install-release.sh to complete init step Because init step need to copy scripts/.env.example, and it usually be ignored, I use Install-release.sh to pack these step. 2. Can modify config.py: Config should be modified, but before we don't do it. 3. Fix backend error: When use docker compose, backend won't connect to db every twice. It's because backend doesn't wait db start. So I fix it.
Here are five things in this commit: 1. Use Install-release.sh to complete init step Init step need to copy scripts/.env.example, but it usually be ignored. Because of this, I use Install-release.sh to pack these step. 2. Can modify config.py: Config should be modified for user, but before we don't do it. 3. Fix backend error: When use docker compose in release version, backend won't connect to db every twice. It's because backend doesn't wait db start. So I fix it. 4. Separate dev and release docker container: When I solving the above tasks, I need to use dev and release in the same time, but the docker container and port are the same. To fix it, I separated them to two independent part. 5. Add watch ./scripts in dev: Like 4. , the dev version should watch the changes in scripts that can know whole change.
Becuase I change the container name on release version for separate dev and release version, the container name on test-docker.yml are wrong.
In test-docker.yml, I just change some 'backend' to 'release-backend', so release build test has error. This commit change all 'backend' to 'release-backend' when it needs.
yushiuan9499
approved these changes
Dec 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
purpose
Let user easier start ntoj when first download.
Fix docker watch problem on dev version and container conflict
changes
Docker release version init & start step
Separate dev and release version container
Docker dev version watch range
New default OJ-problem