From: Russ F. <ru...@to...> - 2006-04-20 19:21:29
|
(Splitting this for the plone-docs list - including attachment it was =20= too big) Interesting, Chris. I'm in the middle of a proposal and only have a moment. Paraphrasing =20 Pascal, this would have been shorter, but I hadn't the time. Attached is a version that has worked for Z2 and recent Plones, and =20 that I've recently hastily modified for Z3, standalone. It's not quality but has served quite well. It used to smartly apply =20 diffs to client and zeo config files, but that was a pain to keep up =20 to date. The precursor was a pure shell script. It was when I moved from that =20 to python that I lost patience with the diff'd config files. The package info that's currently hard coded could easily be external =20= to remove a major source of change in the script itself It's irritating how conventions about .tgz, .tar.gz and version =20 numbering have changed in Plone and Zope. Makes it hard to automate. =20 And sometimes unzipped packages are names a bit different from the =20 tar files they were in. So there's that horrible kludge about =20 building as you'll see. Lots of this could be improved by having some =20= nice managed config info in a public place. Best would be to install by fetching the script and tools from svn. A =20= list of options for bundles could be offered or passed as params. I think it's time to move more to this model (possible exception of =20 Windows) and away from packaged installers which need much =20 maintenance for the value they provide, and only provide a 'getting-=20 started' kind of config. The ones I know seem to put things in /usr/=20 local/zope and forget that there will be multiple concurrent =20 versions, installations, some for testing, some for production ;) - =20 I'm moving over to a setup that facilitates virtual servers- no need =20= to go outside a virt server root, but that can be configured for a =20 'systemwide' installation. other notes; testZEO is the script to start things up. I need (we all need) the ability to have specific python =20 installations to maintain control of special site-package configs. =20 Lots more things coming inside eggs, PIL, SQLObject, etc. I rely on there being a platform python to run all this with. But I =20 never use that to run Zope. in fstools.py curlFile() looks for cached versions of the file to =20 get. Saves some time during testing, while still not needing to rsync =20= from a preloaded server. Now show me yours! ;) --r On 20 Apr 2006, at 19:18, Chris Steel wrote: > > I use a rather kludgy install script I've developed that does a =20 > from-source > build and install of python, zope, plone, linguaplone. > It always creates ZEO client0 and client1. > I find it really useful for dev and debugging, even before we get to > multiprocessor systems and performance. > Each zope install gets its own pet python, so everything is very =20 > controlled, > including python add-ons like PIL. > Would it be worthwhile to recommend ZEO clients as a standard part =20 > of server > setup? > --r > > Russ, > > I am in the process of building an rsync / ssh script to do the =20 > same thing. > Right now I use it for installing plone products on a remote dev =20 > system. The > script is also "rather clunky" but gets the job done. Basically it =20= > ssh's > into the server, rsyncs an installation directory and then runs a =20 > script > that was rsynced onto the server with the package. It then installs =20= > the > products, corrects ownership info an so forth. Want to trade =20 > scripts? That > could save me a lot of time and it is basically where I am headed now. > > Thanks, > > Chris Steel > > manoeuvre.org > > > -- > View this message in context: http://www.nabble.com/Server-Guide%3A-=20= > Overview-and-Document-structure-t1472505.html#a4012778 > Sent from the Plone - docs forum at Nabble.com. > =97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97 Russ Ferriday Topia Systems tel: (+44) (0) 2076 177758 mobile: (+44) (0) 7789 338868 web: http://www.topia.com skype: ferriday |