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

Add option to choose live update or stop and start update #6

Open
smpallen99 opened this issue May 27, 2014 · 1 comment
Open

Add option to choose live update or stop and start update #6

smpallen99 opened this issue May 27, 2014 · 1 comment

Comments

@smpallen99
Copy link
Owner

The spec file currently does a live update. I would like an option to create a spec file that does a stop service, update, start server for cases where the release does not work with live updates.

I would like the default to be stop and start. This way, the developer is forced to think about whether or not their project supports live update.

I know that I just had a problem with a r Module while working on a change. I had chanced the schema of a gen_server stata_data struct and my gen_server crashed after reloading. So, I believe the safer default is to stop update and restart the service during the rpm installation

@bitwalker what do you think about this default?

@bitwalker
Copy link

That seems like a good idea to me. The appups I generate by default via exrm are not super smart - they are about as good as it's possible to get without manually writing one though. For simple cases, live upgrades should work as expected, but for the more general case, and in my opinion, the more likely case - they are just a good starting point, manual work is still needed for each upgrade.

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

No branches or pull requests

2 participants