Hacker News new | past | comments | ask | show | jobs | submit login

After you've done releases a few times, it ends up being quite easy. The biggest issues I had was complete release (aka erlang itself) updates.

Admittedly, I didn't have a whole company core product riding on my upgrades.




We just pushed code, compiled, and hotloaded... Pretty much ignoring the release files; we had them, but I think the contents weren't correct and we never changed the release numbers, etc.

For otp updates, we would shutdown beam in an orderly fashion, replace the files, and start again. (Potentially installing the new one before shutting down, I can't remember).

Post facebook, more of boring OS packages and slow rollouts than hotloading.


Thank you for providing the information, its always good to see how others were rolling out updates.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: