[email protected] wrote:
On Tue, 20 Mar 2012, Miles Fidelman wrote:
[email protected] wrote:
Pretty much ok on 1-3, 4 and 5 are what I'm focusing on right now.
Right now, most of my build and config takes the form of fairly
simple checklists, containing steps like:
- apt-get install <foo> (or: download; untar; ./configure, ./make,
./make test, ./make install)
- look up some config info (e.g., pull an unused IP address off a
checklist)
- add a domain record to a zone file
- edit one or more config files
- ,/init.d/<foo> start
other than editing config config files, pretty much everything
consists of one-line shell commands - easy enough to stick into a
bash script; and I guess a lot of the configuration could be done by
adding sed commands to the script
thinking more and more that rundeck (or something like it) would make
it easy to manage and execute those scripts (the other thing that
looks pretty interesting is a little project called sm-framework
(https://sm.beginrescueend.com/presentations/SM-Framework-Presentation.pdf)
- essentially adds some glue to the zsh and treats scripts like plug-ins
One problem with just automating apt-get install <foo> is that you
don't know what version of <foo> will be installed. It will be the
latest one in the repository you are pointing at (by default the
upstream project). In development this is fine, but in production this
can be a problem.
Point taken.
Thanks!
Miles
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
_______________________________________________
Tech mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
