I understand your concern. While updating it, I had given some thought to whether or not I should embed specific versions into the script. I opted to include them directly in the file so that, getting started, you would be using a "tested" set of support applications if the OS you were running required you to install them yourself. If the OS has newer versions provided by default or via an update, those will be used instead. Also, if you know enough to desire a specific version, you can probably modify the script to the version you prefer. :)
If we wanted to parameterize it, I would opt for optional command line parameters that would default to a version that most people agree is the most "ideal". I hadn't considered if someone would be running it multiple times and wanted to keep all pre-existing versions of welcome.conf. If it is desired, it would be quick to move it over to a date stamped backup file. A large part of updating the script was to make it easier to get things up and running quickly and correctly with the script acting as a record of what needed to happen to get there. (Including some of the less common things like SELinux or afterthoughts like iptables.) After that, hopefully, the person running it can start to tweak things here and there to their individual liking. Thanks for the feedback! Jeff On Oct 10, 2:52 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > On Oct 10, 2010, at 2:29 PM, berubejd wrote: > > > > > I have created an updated script for Fedora/CentOS/RedHat and done > > testing on the OSs which I have available to me. (Not very > > exhaustive, however.) The script has both been forwarded to Massimo > > and posted on web2pyslices at: > > > http://web2pyslices.com/main/slices/take_slice/98 > > > I have used it a number of times and I haven't encountered any issues. > > A couple of comments. > > Ideally, the Python version(s) should be parameterized. I assume, for > example, that we'd want to use 2.6.6 rather than 2.6.4, and it'd be easier to > do those updates if the version were not embedded in the code. Likewise 2.6 > vs 2.7? > > Likewise the mod_wsgi version. > > The old /etc/httpd/conf.d/welcome.conf will be obliterated if the script is > run twice. Maybe we don't care... > > Big improvement; thanks.
