Allow appending `docker compose up` args like `--force-recreate` to the default command of compose type
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
Right now, when I use a dev or latest tag and uploads a new container image to overwrite existing one, clicking deploy/reload button doesn't recreate the running container. This also makes the autodeploy check useless because it cannot replace old container.
I can modify the command to include --force-recreate in the Advanced tab, but that's not the best practice because the command contains the compose file path, which is dynamic and depends on the General tab, which means once I change the compose file path in General tab but not the custom command, and the old compose file path still exists, it can lead to very-hard-to-debug situation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the compose deployment type and the command handling used by the General and Advanced tabs. Start by tracing the deploy/reload path and autodeploy check, then verify that additional docker compose up arguments such as --force-recreate are appended without losing the dynamically selected compose file path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100