It is my understanding that chef is generally used to define a system and
deploy to a node.
Are there use cases where one can package the entire system as an .rpm, .deb,
.exe, etc?
For example, given a simple stack:
How can one package all three into a .rpm so that when given to a customer,
they can install the rpm while still being firewalled from the outside world?
On Thu, Oct 20, 2011 at 2:13 PM, eric.l.m.thomas@gmail.com wrote:
For example, given a simple stack:
- apache2
- mysql
- simple rails application
How can one package all three into a .rpm so that when given to a customer,
they can install the rpm while still being firewalled from the outside world?
You could use Chef to build such a system, then use another tool like
FPM to package the results or create those packages by hand the old
fashioned way.
That said, I'd recommend against it. If the customer ever makes a
change, you lose the configuration management. At least give them the
Chef cookbooks and have them run on their systems using chef-solo.
Bryan