Stop generateconfig-anyconf and generateconfig-processing after usage

anyproto / any-sync-dockercompose

docker-compose for testing any-sync

MIT License

339 stars 43 forks source link

Stop generateconfig-anyconf and generateconfig-processing after usage #76

Closed hellodword closed 1 month ago

hellodword commented 3 months ago

[x] I understand that contributing to this repository will require me to agree with the CLA

Description

small changes

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑‍💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[x] 🤖 Build
[ ] 🔁 CI

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 tech-docs
[ ] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

fb929 commented 3 months ago

this is required for the correct startup sequence

hellodword commented 3 months ago

https://docs.docker.com/compose/compose-file/05-services/#long-syntax-1

service_completed_successfully: Specifies that a dependency is expected to run to successful completion before starting a dependent service.

I think this does not change the startup sequence

fb929 commented 3 months ago

https://docs.docker.com/compose/compose-file/05-services/#long-syntax-1

service_completed_successfully: Specifies that a dependency is expected to run to successful completion before starting a dependent service.

I think this does not change the startup sequence

https://docs.docker.com/compose/compose-file/05-services/#long-syntax-1

service_completed_successfully: Specifies that a dependency is expected to run to successful completion before starting a dependent service.

I think this does not change the startup sequence

ok, we will check