4 ms·
The problem of replicating environments was already a solved issue for me. When I'm setting up an environment for the first time, I make note of all of the comm
by jrogers65 14y ago
The problem of replicating environments was already a solved issue for me. When I'm setting up an environment for the first time, I make note of all of the commands required to set it up and put them in a shell script. I guess it's nice to not have to tweak them when there's an OS upgrade.
The other side of solving this is writing tests to check that, for instance, a particular language extension is loaded. The application should be throwing a fit if something is missing in the environment.
- mitchty 14y agoNo arguments there. All this is is just chef recipes to do basically that. This blog post is a good start but if you have an osx environment you can setup netboot and have a truly automatic install+setup with chef. I'm a bigger fan of using chef/puppet/whatever over personal shell scripts as then you can test your automation out in a vm. I just build osx vm's and validate my osx automation with that.
- udp 14y agoThat shell script will be no good on Windows, which was your other recommendation to replace OS X.