3 ms·
We've been putting our code in rpms and it works well. Every box knows exactly what's deployed right now (along with dependencies and whether anything is tweake
by prodigal_erik 17y ago
We've been putting our code in rpms and it works well. Every box knows exactly what's deployed right now (along with dependencies and whether anything is tweaked), local edits to config files can be preserved, and "ssh yum install" gets a box from clean to production ready in under a minute.
- peterwwillis 17y agoWait - preserve local edits? That sounds bad. It is a handy tool for dealing with versioning and rollback. But i'd hate to be the guy who deploys a hot fix and suddenly rpm is out of locker entries.
- prodigal_erik 17y agoRenaming local edits out of the way or preserving them is up to you, depending on whether you put %config or %config(noreplace) in the spec. It does need to be handled carefully, but it can be handy if you want one machine giving special treatment to a representative sample of your requests or something.