4 ms·
No, definitely not on every deploy! For a deploy, I just do a "git pull" on all of the production boxes and restart the web server. Baking a new AMI only happe
by adrianh 13y ago
No, definitely not on every deploy! For a deploy, I just do a "git pull" on all of the production boxes and restart the web server.
Baking a new AMI only happens when there are new underlying dependencies, like a new package from apt-get or a new Python module from pip. In other words, it's rare.
Hope that helps!
- slig 13y agoIs there any reason for not letting pip update things automagically from your `prod_requirements.txt` using a simple fabric `fab update_pip` when necessary?
- adrianh 13y agoYes, in fact that's what I do! The issue is I need to account for any new servers that might spin up later (hence updating the AMI). I could also change the AMI's "user data" to run pip when the instance loads, but I'm not 100% confident it will always run without errors. I feel better doing it manually and baking it into the AMI. Personal taste.