Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Daemon autoreload stopped working after #365 #416

Open
msm-cert opened this issue Oct 2, 2024 · 1 comment
Open

Daemon autoreload stopped working after #365 #416

msm-cert opened this issue Oct 2, 2024 · 1 comment
Assignees
@michalkrzem
Labels
priority:low Priority: low type:bug Something isn't working zone:backend Backend oriented tasks
Milestone
v1.5.0

Comments

@msm-cert
Copy link
Member

msm-cert commented Oct 2, 2024 •
edited
Loading

After #365, daemon autoreload in dev docker-compose stopped working. This should be fixed.

(Also maybe there are better ways to achieve this now, without manual scripts?)
@msm-cert msm-cert added type:bug Something isn't working priority:low Priority: low zone:backend Backend oriented tasks labels Oct 2, 2024
@msm-cert msm-cert added this to the Sprint 1 milestone Oct 17, 2024
@msm-cert
Copy link
Member Author

The only goal of this PR is to have worker/daemon automatically reload when running docker-compose.dev.yml and code changes. It's OK to use something different than the autoreload script that was used before. It's also ok to use external dependency for this, if something like this exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michalkrzem michalkrzem

Labels
priority:low Priority: low type:bug Something isn't working zone:backend Backend oriented tasks
Projects
None yet
Milestone
v1.5.0
Development

No branches or pull requests
2 participants
@michalkrzem @msm-cert