From: Chabbrik <vas...@gm...> - 2006-04-19 05:57:35
|
This post will describe what manuals/how-tos/tutorials relevant to Server setup I managed to discover on plone.org so far. Also, it should be pointed out, that current documents usually lack a lot of context and assume a lot of things. My suggestion would be that the only assumption to be taken into account would be that services are installed with default configuration. This is a necessary assumption because it would be next to impossible to cover all possible ways of installation software, especially in Linux environment. Every author would specify the configuration (OS, maybe kernel version, services versions) he used while writing his guide/howto. Also a mean should be discussed and agreed upon how other people could report whether it worked or didn't work on their configuration. So without further ado, I would like to present my vision of Server Guide. 1 Introduction (Some generic information, purpose of this document, credits, etc) 2 Basic Setup (Some basic information that would be important to everybody willing to start playing with Zope/Plone) 2.1 Setting up Zope & Plone (This section si fine, maybe a bit of clean-up is required) Sources: http://plone.org/documentation/how-to/setup-from-source http://www.plope.com/Books/2_7Edition/InstallingZope.stx 2.2 Adding more Products (I suggest merging those two documents into one) Sources: http://plone.org/documentation/tutorial/third-party-products http://plone.org/documentation/how-to/installing-products 2.3 [Suggestions???] 3 Server Setup (This section covers basic server configuration that would be enough for small websites with little load) 3.1 Backups (This document is nice as is, maybe some clean-up and it can be included into this guide) Sources: http://plone.org/documentation/how-to/quickie-plone-backup-using-repozo 3.2 Integration with Apache There are lot of documents related to this topics on both zope.org and plone.org. My suggestion they should be (at least plone.org docs) organised into a single document for better maintanability and ease of use. Sources: http://plone.org/documentation/how-to/apache-ssl http://plone.org/documentation/tutorial/plone-apache http://plone.org/documentation/tutorial/robust-installation/ http://plone.org/documentation/how-to/mixing-apache-and-plone http://plone.org/documentation/how-to/plone-with-apache-1.3 http://www.zope.org/Members/regebro/Zope_and_Apache http://www.zope.org/Members/mwr/VHosts_With_Zope_Default http://zope.org/Documentation/Books/ZopeBook/2_6Edition/VirtualHosting.stx http://www.cheimes.de/opensource/docs/zope-apache2/ http://www.zope.org/Members/regebro/Zope_and_Apache 3.3 MailHost This section is quite debatable. I would like to see there how to setup mail server that can be then used with Plone site. However there are a few issues to tackle. What MTA should we choose? Is it that relevant to Plone? At the very least, IMHO, we should describe how to properly setup MailHost in Zope. It is not very clear to me at the moment. 3.4 ZoDB Auto-Pack script/procedure There is no such thing at the moment, or I was just unable to find it. I'm not sure if it is important to have, but I thought it would be nice to schedule this sort of things. 3.5 LDAP integration (This section might as well be moved to Advanced Setup) This is a very important document that should written as clear as possible. However, it should not be included into this guide, because it is a part of LDAP/PAS/AUTH guide, so it should just refer there. 3.6 [Suggestions???] 4 Advanced Server Setup (This section is dedicated to more complex configurations and usually required by bigger and more heavy-loaded sites) [I would like more suggestions on this section, as I have very little experience with this sort of websites and do not really know their needs] 4.1 Caching Sources: http://plone.org/documentation/tutorial/optimizing-plone/ http://plone.org/documentation/how-to/squid-integration-pointers http://plone.org/documentation/how-to/cache-content 4.2 Clustering Sources: http://plone.org/documentation/how-to/simple-zope-clustering-with-squid-and-pound 4.3 RDBMS integration (MySQL/Postgres) It should not be a section of this guide, rather a link to the guide currently in development. It has has to be, because to my mind it seems related to server setup as well. 4.4 [Suggestions???] -- View this message in context: http://www.nabble.com/Server-Guide%3A-Overview-and-Document-structure-t1472505.html#a3982029 Sent from the Plone - docs forum at Nabble.com. |
From: Martin A. <opt...@gm...> - 2006-04-19 11:24:56
|
Chabbrik wrote: > > This post will describe what manuals/how-tos/tutorials relevant to Server > setup I managed to discover on plone.org so far. > Also, it should be pointed out, that current documents usually lack a lot > of context and assume a lot of things. > My suggestion would be that the only assumption to be taken into account > would be that services are installed with default configuration. This is a > necessary assumption because it would be next to impossible to cover all > possible ways of installation software, especially in Linux environment. > Every author would specify the configuration (OS, maybe kernel version, > services versions) he used while writing his guide/howto. Also a mean > should be discussed and agreed upon how other people could report whether > it worked or didn't work on their configuration. > Excellent work, Vasily. :-) I suggest that you go ahead and create a Reference Manual on plone.org/documentation/manual and create sections and pages to get the basic structure in place. We can then start to flesh it out. Some comments below: > So without further ado, I would like to present my vision of Server Guide. > 1 Introduction (Some generic information, purpose of this document, > credits, etc) > 2 Basic Setup (Some basic information that would be important to > everybody willing to start playing with Zope/Plone) > 2.1 Setting up Zope & Plone (This section si fine, maybe a bit of > clean-up is required) > Sources: > http://plone.org/documentation/how-to/setup-from-source > http://www.plope.com/Books/2_7Edition/InstallingZope.stx > Good so far. I'd say that "basic setup" will need to be carefully structured so that we point out that the blind install from source or using the installers misses out things like ZEO. > 2.2 Adding more Products (I suggest merging those two documents into one) > Sources: > http://plone.org/documentation/tutorial/third-party-products > http://plone.org/documentation/how-to/installing-products > They should. However, I think we should leave the tutorial where it is, retire the how-to after resolving any missing parts in the tutorial, and then just link to it from the server setup guide, because the tutorial is useful for people evaluating third party products in general, not just for server setup. Having a page that's pretty much just a paragraph + a link is fine. > 2.3 [Suggestions???] > 3 Server Setup (This section covers basic server configuration that would > be enough for small websites with little load) > 3.1 Backups (This document is nice as is, maybe some clean-up and it can > be included into this guide) > Sources: > http://plone.org/documentation/how-to/quickie-plone-backup-using-repozo > 3.2 Integration with Apache > There are lot of documents related to this topics on both zope.org and > plone.org. My suggestion they should be (at least plone.org docs) > organised into a single document for better maintanability and ease of > use. > Sources: > http://plone.org/documentation/how-to/apache-ssl > http://plone.org/documentation/tutorial/plone-apache > http://plone.org/documentation/tutorial/robust-installation/ > http://plone.org/documentation/how-to/mixing-apache-and-plone > http://plone.org/documentation/how-to/plone-with-apache-1.3 > http://www.zope.org/Members/regebro/Zope_and_Apache > http://www.zope.org/Members/mwr/VHosts_With_Zope_Default > http://zope.org/Documentation/Books/ZopeBook/2_6Edition/VirtualHosting.stx > http://www.cheimes.de/opensource/docs/zope-apache2/ > http://www.zope.org/Members/regebro/Zope_and_Apache > This is the one we really need to get right. We need clear instructions with sufficient background, focusing on the most common case: using RewriteRules with Zope and Apache on the same host, but giving enough details for more specific setup. We also need a section on hosting behind Squid, using CacheFu, at the same level as the section on Apache - people usually choose one or the other. Then we need a final section showing how to use both (Squid -> Apache -> Zope). Note that the CacheFu docs are pretty good - see http://svn.plone.org/svn/collective/CacheFu/trunk Then we need a section on how this stuff works with IIS on Windows. The generic Apache and Squid sections need to cover Windows and *nix equally. > 3.3 MailHost > This section is quite debatable. I would like to see there how to setup > mail server that can be then used with Plone site. However there are a few > issues to tackle. What MTA should we choose? Is it that relevant to Plone? > At the very least, IMHO, we should describe how to properly setup MailHost > in Zope. It is not very clear to me at the moment. > I'm not sure we should be documenting how to set up sendmail or postfix, since that's not very Plone specific. Setting up a mail host isn't that hard, actually, but a page on it would be nice. > 3.4 ZoDB Auto-Pack script/procedure > There is no such thing at the moment, or I was just unable to find it. I'm > not sure if it is important to have, but I thought it would be nice to > schedule this sort of things. > Sounds good. Perhaps not as urgent as the other sections, though. > 3.5 LDAP integration (This section might as well be moved to Advanced > Setup) > This is a very important document that should written as clear as > possible. However, it should not be included into this guide, because it > is a part of LDAP/PAS/AUTH guide, so it should just refer there. > Ben Mason is in the process of writing an LDAP tutorial, and I think this should stand alone, since it's useful to people just configuring LDAP. A link would be good, though. Helping Ben would be good too :) > 3.6 [Suggestions???] > 4 Advanced Server Setup (This section is dedicated to more complex > configurations and usually required by bigger and more heavy-loaded sites) > [I would like more suggestions on this section, as I have very little > experience with this sort of websites and do not really know their needs] > 4.1 Caching > Sources: > http://plone.org/documentation/tutorial/optimizing-plone/ > http://plone.org/documentation/how-to/squid-integration-pointers > http://plone.org/documentation/how-to/cache-content > Check out the CacheFu docs. I think that with CacheFu, squid isn't so "advanced" anymore, and should probably be recommended alongside Apache - it makes a big difference. > 4.2 Clustering > Sources: > http://plone.org/documentation/how-to/simple-zope-clustering-with-squid-and-pound > Very interesting. We need to cover ZEO, though again, I think this isn't so "advanced" - it's highly recommended even for small sites. We may want to consider distinguishing between the small-to-medium scenario of putting two ZEO instances on one machine and the more advanced scenario of having many machines across a network. > 4.3 RDBMS integration (MySQL/Postgres) > It should not be a section of this guide, rather a link to the guide > currently in development. It has has to be, because to my mind it seems > related to server setup as well. > Agree. Hopefully Philip & co will have something on this soon. Great work consolidating the existing resources. Let's get started and work out the details as we go along. :) Martin -- View this message in context: http://www.nabble.com/Server-Guide%3A-Overview-and-Document-structure-t1472505.html#a3985629 Sent from the Plone - docs forum at Nabble.com. |
From: Russ F. <ru...@to...> - 2006-04-19 11:33:06
|
On 19 Apr 2006, at 12:24, Martin Aspeli wrote: > > Good so far. I'd say that "basic setup" will need to be carefully =20 > structured > so that we point out that the blind install from source or using the > installers misses out things like ZEO. I use a rather kludgy install script I've developed that does a from-=20 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 =20 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 of =20= server setup? --r =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 |
From: Jean J. <je...@up...> - 2006-04-19 11:44:07
|
> Would it be worthwhile to recommend ZEO clients as a standard part of > server setup? From my perspective I'd say yes. I'm never glad I skipped ZEO setup; on the contrary, I always rue it eventually. It is one more port and one more config twiddle and one more service to start, though. Perhaps "standard" should be with ZEO, and "toy" should be without ;-> -- Jean Jordaan http://www.upfrontsystems.co.za |
From: Martin A. <opt...@gm...> - 2006-04-19 11:56:50
|
Russ Ferriday wrote: > > I use a rather kludgy install script I've developed that does a 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 > controlled, including python add-ons like PIL. > Would it be worthwhile to recommend ZEO clients as a standard part of > server setup? > Yes, it is. ZEO is good practice. Also, I believe skeletor can (will?) be able to set it all up for you very easily. We may want to recommend that. Whit and Ben should know more about what state it's in. Martin -- View this message in context: http://www.nabble.com/Server-Guide%3A-Overview-and-Document-structure-t1472505.html#a3986028 Sent from the Plone - docs forum at Nabble.com. |
From: Chris S. <chr...@gm...> - 2006-04-20 18:18:24
|
I use a rather kludgy install script I've developed that does a 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 controlled, including python add-ons like PIL. Would it be worthwhile to recommend ZEO clients as a standard part of server setup? --r Russ, I am in the process of building an rsync / ssh script to do the same thing. Right now I use it for installing plone products on a remote dev system. The script is also "rather clunky" but gets the job done. Basically it ssh's into the server, rsyncs an installation directory and then runs a script that was rsynced onto the server with the package. It then installs the products, corrects ownership info an so forth. Want to trade 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-Overview-and-Document-structure-t1472505.html#a4012778 Sent from the Plone - docs forum at Nabble.com. |
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 |
From: Russ F. <ru...@to...> - 2006-04-20 19:22:19
|
Interesting, Chris.<snip> Now show me yours! ;) --r =EF=BF=BC =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2= =80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80= =94=E2=80=94=E2=80=94=E2=80=94=E2=80=94 Russ Ferriday Topia Systems tel: (+44) (0) 2076 177758 mobile: (+44) (0) 7789 338868 web: http://www.topia.com skype: ferriday |
From: Chris S. <chr...@gm...> - 2006-04-21 04:12:04
Attachments:
plone-autoinstaller.tar.gz
|
Hi Russ, Thanks! I am going to try it out. Here is mine. I started this script in order to rapidly re-create identical instances on multiple systems so that everyone here had the same setups for testing, they could break them and set them back up identically at will. I used a small collection of install instructions as a reference for installing plone products of interest to us. (a fine example of the variety of compression formats, directory structures and so on you mentioned). Lately I have been reading a lot of python and have been preparing to move the script(s) to python once I finished working through the best ways to install zope and so forth and then the original shell script would (will?) be changed into a python installer {but who really needs a python installer script - smirk} ). The "I have nothing better to do right now" horizon project being a plone archetype for a web based recipe / check box system for automating installations (or for the more prudent traveller the creation of install scripts) server / plone / plone product / what ever installer page thingy. The python seems to have gotten a rather serious hold of everyone here at the moment so perhaps I will forget about some of my personal deadlines and submit to it's grasp myself sooner rather than later. {sigh} FYI - my script uses rsync in, shall I say a rather unorthodox manner, it syncs an installation "package" (a folder with an installation script set and components and config files) rather than syncing a "server" per say. It is not very pretty, but it is really fast, old school type script. Cheers, Chris Steel Manoeuvre.org On 4/20/06, Russ Ferriday <ru...@to...> wrote: > Interesting, Chris. > I'm in the middle of a proposal and only have a moment. Paraphrasing Pasc= al, > this would have been shorter, but I hadn't the time. > Attached is a version that has worked for Z2 and recent Plones, and that > I've recently hastily modified for Z3, standalone. > It's not quality but has served quite well. It used to smartly apply diff= s > to client and zeo config files, but that was a pain to keep up to date. > The precursor was a pure shell script. It was when I moved from that to > python that I lost patience with the diff'd config files. > The package info that's currently hard coded could easily be external to > remove a major source of change in the script itself > It's irritating how conventions about .tgz, .tar.gz and version numbering > have changed in Plone and Zope. Makes it hard to automate. And sometimes > unzipped packages are names a bit different from the tar files they were = in. > So there's that horrible kludge about building as you'll see. Lots of thi= s > could be improved by having some nice managed config info in a public pla= ce. > Best would be to install by fetching the script and tools from svn. A lis= t > 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 Windo= ws) > and away from packaged installers which need much maintenance for the val= ue > they provide, and only provide a 'getting-started' kind of config. The on= es > I know seem to put things in /usr/local/zope and forget that there will b= e > multiple concurrent versions, installations, some for testing, some for > production ;) - I'm moving over to a setup that facilitates virtual serve= rs- > no need to go outside a virt server root, but that can be configured for= a > 'systemwide' installation. > other notes; > testZEO is the script to start things up. > I need (we all need) the ability to have specific python installations to > maintain control of special site-package configs. Lots more things coming > inside eggs, PIL, SQLObject, etc. > I rely on there being a platform python to run all this with. But I never > use that to run Zope. > in fstools.py curlFile() looks for cached versions of the file to get. > Saves some time during testing, while still not needing to rsync 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 from-sour= ce > 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 controll= ed, > including python add-ons like PIL. > Would it be worthwhile to recommend ZEO clients as a standard part of ser= ver > setup? > --r > > Russ, > > I am in the process of building an rsync / ssh script to do the same thin= g. > Right now I use it for installing plone products on a remote dev system. = The > script is also "rather clunky" but gets the job done. Basically it ssh's > into the server, rsyncs an installation directory and then runs a script > that was rsynced onto the server with the package. It then installs the > products, corrects ownership info an so forth. Want to trade scripts? Th= at > 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-Overview-and-Document-structure-t14= 72505.html#a4012778 > Sent from the Plone - docs forum at Nabble.com. > > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim= o > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > Plone-docs mailing list > Plo...@li... > https://lists.sourceforge.net/lists/listinfo/plone-docs > > > > > =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 > > > > |
From:
<chr...@ma...> - 2006-04-21 21:26:30
|
Hi, I'm not a programmer but I find this script from Tomster. http://tomster.org/blog/archive/2005/10/16/instant-plone/ It may be usefull (or not) Christophe Chris Steel a =E9crit : >Hi Russ, > >Thanks! I am going to try it out. Here is mine. > >I started this script in order to rapidly re-create identical >instances on multiple systems so that everyone here had the same >setups for testing, they could break them and set them back up >identically at will. I used a small collection of install instructions >as a reference for installing plone products of interest to us. (a >fine example of the variety of compression formats, directory >structures and so on you mentioned). Lately I have been reading a lot >of python and have been preparing to move the script(s) to python once >I finished working through the best ways to install zope and so forth >and then the original shell script would (will?) be changed into a >python installer {but who really needs a python installer script - >smirk} ). The "I have nothing better to do right now" horizon project >being a plone archetype for a web based recipe / check box system for >automating installations (or for the more prudent traveller the >creation of install scripts) server / plone / plone product / what >ever installer page thingy. > >The python seems to have gotten a rather serious hold of everyone here >at the moment so perhaps I will forget about some of my personal >deadlines and submit to it's grasp myself sooner rather than later. >{sigh} > >FYI - my script uses rsync in, shall I say a rather unorthodox manner, >it syncs an installation "package" (a folder with an installation >script set and components and config files) rather than syncing a >"server" per say. It is not very pretty, but it is really fast, old >school type script. > >Cheers, > >Chris Steel > >Manoeuvre.org > >On 4/20/06, Russ Ferriday <ru...@to...> wrote: > =20 > >>Interesting, Chris. >>I'm in the middle of a proposal and only have a moment. Paraphrasing Pa= scal, >>this would have been shorter, but I hadn't the time. >>Attached is a version that has worked for Z2 and recent Plones, and tha= t >>I've recently hastily modified for Z3, standalone. >>It's not quality but has served quite well. It used to smartly apply di= ffs >>to client and zeo config files, but that was a pain to keep up to date. >>The precursor was a pure shell script. It was when I moved from that to >>python that I lost patience with the diff'd config files. >>The package info that's currently hard coded could easily be external t= o >>remove a major source of change in the script itself >>It's irritating how conventions about .tgz, .tar.gz and version numberi= ng >>have changed in Plone and Zope. Makes it hard to automate. And sometime= s >>unzipped packages are names a bit different from the tar files they wer= e in. >>So there's that horrible kludge about building as you'll see. Lots of t= his >>could be improved by having some nice managed config info in a public p= lace. >>Best would be to install by fetching the script and tools from svn. A l= ist >>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 Win= dows) >>and away from packaged installers which need much maintenance for the v= alue >>they provide, and only provide a 'getting-started' kind of config. The = ones >>I know seem to put things in /usr/local/zope and forget that there will= be >>multiple concurrent versions, installations, some for testing, some for >>production ;) - I'm moving over to a setup that facilitates virtual ser= vers- >> no need to go outside a virt server root, but that can be configured f= or a >>'systemwide' installation. >>other notes; >>testZEO is the script to start things up. >>I need (we all need) the ability to have specific python installations = to >>maintain control of special site-package configs. Lots more things comi= ng >>inside eggs, PIL, SQLObject, etc. >>I rely on there being a platform python to run all this with. But I nev= er >>use that to run Zope. >>in fstools.py curlFile() looks for cached versions of the file to get. >>Saves some time during testing, while still not needing to rsync 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 from-so= urce >>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 contro= lled, >>including python add-ons like PIL. >>Would it be worthwhile to recommend ZEO clients as a standard part of s= erver >>setup? >>--r >> >>Russ, >> >>I am in the process of building an rsync / ssh script to do the same th= ing. >>Right now I use it for installing plone products on a remote dev system= . The >>script is also "rather clunky" but gets the job done. Basically it ssh= 's >>into the server, rsyncs an installation directory and then runs a scrip= t >>that was rsynced onto the server with the package. It then installs the >>products, corrects ownership info an so forth. Want to trade 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-Overview-and-Document-structure-t= 1472505.html#a4012778 >>Sent from the Plone - docs forum at Nabble.com. >> >> >> >>------------------------------------------------------- >>Using Tomcat but need to do more? Need to support web services, securit= y? >>Get stuff done quickly with pre-integrated technology to make your job >>easier >>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron= imo >>http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 >>_______________________________________________ >>Plone-docs mailing list >>Plo...@li... >>https://lists.sourceforge.net/lists/listinfo/plone-docs >> >> >> >> >>=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 >> >> >> >> >> =20 >> |
From: Philip K. <ph...@xf...> - 2006-04-19 13:55:12
|
Hi Martin, Martin Aspeli wrote: >> 4.3 RDBMS integration (MySQL/Postgres) >> It should not be a section of this guide, rather a link to the guide >> currently in development. It has has to be, because to my mind it seems >> related to server setup as well. >> > > Agree. Hopefully Philip & co will have something on this soon. > I'm plugging away on this, but it's going to take me a few weeks to get it all done - although I should have the structure in place enough to expose it to the rest of the world after this coming weekend. I wrote a lot of this a long time ago, for a very different audience and with less of an understanding myself, and I'm finding myself unable to resist rewriting much of it as I go. FWIW, in the /set-up/ side of the piece, I discuss: - - egenix mxODBC DA + MS SQL on Windows -- egenix vs. F/OSS ODBC alternatives (they exist, I don't use them because it's not worth the testing when the eGenix product is so inexpensive) -- MS SQL 2000, MS SQL Express (surprisingly useful!) + MS Access and why not to use the JET database engine (I've seen it done, it's not pretty). - Z Psycopg + PostgreSQL -- Including how to set up PG Admin using PuTTY + SSH tunnel as required in a hosted environment (My notes relate to Zettai). - kinterbasdbDA + KInterbasDB + Firebird -- Because it's a good example of a case where there are components at both the Python and Zope level to consider. (I don't discuss mySQL except in passing when listing alternatives, because I don't use it.) Any obvious omissions? -- Regards, PhilK Email: ph...@xf... PGP Public key: http://www.xfr.co.uk Voicemail & Facsimile: 07092 070518 “The creative impulse animates whatever instrument is placed at its disposal.” — Robert Fripp |
From: Alexander L. <li...@pl...> - 2006-04-20 08:34:19
|
On Wed, 19 Apr 2006 15:53:28 +0200, Philip Kilner <ph...@xf...> wrote: > MS Access I thought you were documenting databases? I'm confused. ;) -- _____________________________________________________________________ Alexander Limi · Chief Architect · Plone Solutions · Norway Consulting · Training · Development · http://www.plonesolutions.com _____________________________________________________________________ Plone Co-Founder · http://plone.org · Connecting Content Plone Foundation · http://plone.org/foundation · Protecting Plone |
From: Patrick S. <pad...@gm...> - 2007-01-24 21:30:45
|
Did this document of Philip's ever get published as part of the larger document referred to in this thread or as a stand alone? Thanks, Patrick Smith Hi Martin, Martin Aspeli wrote: >> 4.3 RDBMS integration (MySQL/Postgres) >> It should not be a section of this guide, rather a link to the guide >> currently in development. It has has to be, because to my mind it seems >> related to server setup as well. >> > > Agree. Hopefully Philip & co will have something on this soon. > I'm plugging away on this, but it's going to take me a few weeks to get it all done - although I should have the structure in place enough to expose it to the rest of the world after this coming weekend. I wrote a lot of this a long time ago, for a very different audience and with less of an understanding myself, and I'm finding myself unable to resist rewriting much of it as I go. -- View this message in context: http://www.nabble.com/Server-Guide%3A-Overview-and-Document-structure-tf1472505.html#a8573023 Sent from the Plone - docs mailing list archive at Nabble.com. |
From: Kurt B. <kur...@lo...> - 2006-04-20 19:43:39
|
Hi all, re:>> 3.2 Integration with Apache --------------------------------------- I've started putting a scenario-based framework/outline together for presenting documentation about 'apache/squid/cachefu/ssl' configuration options. Although I'm no "expert", And I'm just starting to look at Geoff's cachefu, I've been banging my head against the wall on these topics long enough that I think I can explain it pretty well to other ploneophytes. I'm willing to take on documenting this, and just as willing to be a part of a larger group to make this happen (my attitude is tempered by my 4-month old daughter's desire to keep me awake all night). So, for what I have so far, is there an "official" process for review, or should I just start posting what I have somewhere and ask this list for ['comments','suggestions','feedback','abuse']? I'd like to start making some solid forward motion building on and also pulling together the excellent efforts in documentation already out there. re:>> 4.2 Clustering --------------------------------------- I've got an installation that is: squid - pound - 4 clients - zeo It seems to work pretty well, and I know there's way more I can do to get it into shape. I'd be glad to share/document what I can on this, as I have to document it anyway for my co-workers in case I get hit by a train or something. Best, Kurt irc: Ku...@ir... --snip-- >Martin Aspeli wrote: > > Chabbrik wrote: >> 3.2 Integration with Apache >>There are lot of documents related to this topics on both zope.org and >>plone.org. My suggestion they should be (at least plone.org docs) >>organised into a single document for better maintanability and ease of >>use. >>Sources: >>http://plone.org/documentation/how-to/apache-ssl >>http://plone.org/documentation/tutorial/plone-apache >>http://plone.org/documentation/tutorial/robust-installation/ >>http://plone.org/documentation/how-to/mixing-apache-and-plone >>http://plone.org/documentation/how-to/plone-with-apache-1.3 >>http://www.zope.org/Members/regebro/Zope_and_Apache >>http://www.zope.org/Members/mwr/VHosts_With_Zope_Default >>http://zope.org/Documentation/Books/ZopeBook/2_6Edition/VirtualHosting.stx >>http://www.cheimes.de/opensource/docs/zope-apache2/ >>http://www.zope.org/Members/regebro/Zope_and_Apache >> > > > This is the one we really need to get right. We need clear instructions with > sufficient background, focusing on the most common case: using RewriteRules > with Zope and Apache on the same host, but giving enough details for more > specific setup. > > We also need a section on hosting behind Squid, using CacheFu, at the same > level as the section on Apache - people usually choose one or the other. > Then we need a final section showing how to use both (Squid -> Apache -> > Zope). > > Note that the CacheFu docs are pretty good - see > http://svn.plone.org/svn/collective/CacheFu/trunk > > Then we need a section on how this stuff works with IIS on Windows. The > generic Apache and Squid sections need to cover Windows and *nix equally. --snip-- >> 4.2 Clustering >>Sources: >>http://plone.org/documentation/how-to/simple-zope-clustering-with-squid-and-pound >> > > > Very interesting. We need to cover ZEO, though again, I think this isn't so > "advanced" - it's highly recommended even for small sites. We may want to > consider distinguishing between the small-to-medium scenario of putting two > ZEO instances on one machine and the more advanced scenario of having many > machines across a network. --snip-- |
From: Martin A. <opt...@gm...> - 2006-04-21 22:55:15
|
> So, for what I have so far, is there an "official" process for review, > or should I just start posting what I have somewhere and ask this list > for ['comments','suggestions','feedback','abuse']? I'd like to start > making some solid forward motion building on and also pulling together > the excellent efforts in documentation already out there. Hi guys, limi and I and a bunch of other people will be away for a week in Norway with limited internet access. What I'd suggest is that you guys hash out a structure you believe will work on this list, then set up a reference manual on plone.org/documentation/manual. The creator uses the 'sharing' tab to give the other guys access, and you can collaborate. A few goals: - All the existing manuals should be consolidated unless they're significantly specialised - Be pragmatic. Cover the most important configurations, not every random combination you can think of. - Promote simplicity - say up front what the recommended way is, and document that primarily. Don't require people to read too much or guess what they should do. - Keep it short and succinct, but make sure you don't make assumptions that people know how Squid or Apache or zope.conf or RAM cache managers or pound or anything else works. Explain what's necessary, and point to wider documentation if necessary. Thank you for running with this! The community really appreciates it! Martin -- (muted) |
From: Chabbrik <vas...@gm...> - 2006-04-21 10:32:56
|
I've put up some sort of roster, taking into account the replies received. It is not a commitment for the people mentioned, but rather a pointer, that somebody offered to work on this section. Concerning my deadlines. Since I'm currently commited to the Plone-based project, I will be working on LDAP, so I will be contributing to those docs. It will last until the start of June the latest. So, In July I suppose I will be fully available to concentrate on this guide and hope to do it in a week or two. I'm taking more easy tasks there first to learn the ropes and get acquainted to the documentation development process. Once I get my feet wet, I hope to contribute to more 'advanced' (for me) topics as well. Roster: 1 Introduction (Some generic information, purpose of this document, credits, etc) 2 Basic Setup Vasily Savin (I'm taking the whole section.) 2.1 Setting up Zope & Plone 2.2 Adding more Products 3 Server Setup 3.1 Backups Vasily Savin 3.2 Integration with Apache - Kurt Bendl 3.3 MailHost 3.4 ZoDB Auto-Pack script/procedure Vasily Savin (There was a nice example in Zope Book I think, I will test it and submit for review) 3.5 LDAP integration 3.6 ZEO 4 Advanced Server Setup 4.1 Caching - Kurt Bendl 4.2 Clustering - Kurt Bendl 4.3 RDBMS integration (MySQL/Postgres) - Philip Kilner -- View this message in context: http://www.nabble.com/Server-Guide%3A-Overview-and-Document-structure-t1472505.html#a4023964 Sent from the Plone - docs forum at Nabble.com. |
From: Patrick S. <pad...@gm...> - 2007-01-24 21:58:17
|
Did this document ever make it up to the plone site? I'm particularly interested in the rdbms aspect of it that is referred to below. Thanks, Patrick Smith Vasily Savin wrote: > > This post will describe what manuals/how-tos/tutorials relevant to Server > setup I managed to discover on plone.org so far. > Also, it should be pointed out, that current documents usually lack a lot > of context and assume a lot of things. > My suggestion would be that the only assumption to be taken into account > would be that services are installed with default configuration. This is a > necessary assumption because it would be next to impossible to cover all > possible ways of installation software, especially in Linux environment. > Every author would specify the configuration (OS, maybe kernel version, > services versions) he used while writing his guide/howto. Also a mean > should be discussed and agreed upon how other people could report whether > it worked or didn't work on their configuration. > So without further ado, I would like to present my vision of Server Guide. > ... > 4.3 RDBMS integration (MySQL/Postgres) > It should not be a section of this guide, rather a link to the guide > currently in development. It has has to be, because to my mind it seems > related to server setup as well. > ... > -- View this message in context: http://www.nabble.com/Server-Guide%3A-Overview-and-Document-structure-tf1472505.html#a8572843 Sent from the Plone - docs mailing list archive at Nabble.com. |
From: Martin A. <opt...@gm...> - 2007-01-25 08:48:43
|
Patrick Smith wrote: > Did this document ever make it up to the plone site? > > I'm particularly interested in the rdbms aspect of it that is referred to > below. Nope. No-one has done this work yet. Martin |