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.

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

Air should support executing binary again when executable exit #353

Closed
tymonx opened this issue Nov 15, 2022 · 1 comment · Fixed by #363
Closed

Air should support executing binary again when executable exit #353

tymonx opened this issue Nov 15, 2022 · 1 comment · Fixed by #363

Comments

@tymonx
Copy link

tymonx commented Nov 15, 2022

Currently it doesn't execute binary again when exit. It does only when file changes. Air should exit with the same status code as exited binary OR rerun binary again with optional configurable delay. Both features should be configurable and may be disabled on default to keep backward compatibility.

Use case:
Microservices or long-running applications can be run as services under Docker Compose with the restart: always option, Docker Swarm or other container orchestration solution. For development purpose Air can be also run in these environments. But some applications/frameworks terminate running application for example because of unreachable message broker or database service instance. And orchestration rerun them again. But with Air it never happens. Because Air never exit or rerun binary when binary exit by itself.

@xiantang
Copy link
Collaborator

good feature.
So air needs to check whether the process is alive, if not alive air should restart the process.
I will do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants