Changes between Version 50 and Version 51 of WikiStart


Ignore:
Timestamp:
12/08/10 11:34:34 (9 years ago)
Author:
gracinet
Comment:

Mentionned Debian package, more details about ?branch, uniformity and cut mkcpsdevinstance section in two

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v50 v51  
    3333 
    3434 
    35 === Automated process === 
     35=== Automated process: mkcpsdevinstance === 
    3636 
    37 As of #2206, CPS comes with a script that creates a Zope instance, sets up its Products directory as a HgBundler bundle and creates a CPS portal in it.  
     37As of #2206, CPS comes with the ```mkcpsdevinstance``` script, that creates a Zope instance, sets up its Products directory as a HgBundler bundle and creates a CPS portal in it.  
     38 
     39==== installation ==== 
    3840 
    3941Prerequisites: 
     
    4951}}} 
    5052 
     53If you are running Debian 5.0 (lenny), a useful alternative is to use our Debian packages [http://www.racinet.fr/index.php?pages/Debian-packages setup instructions]. To get a working ```mkcpsdevinstance``` in ```/opt/cps-3.5/bin```, with all required dependencies, just do: 
     54 
     55{{{ 
     56   $ sudo aptitude install opt-zope-cps-3.5-devsetup 
     57}}}  
     58 
     59 
     60===== Usage ===== 
     61 
     62From now on, we assume that ```mkcpsdevinstance``` is on the system PATH. 
     63 
    5164To create a CPS-3-full instance in ```/var/opt```: 
    5265{{{ 
    53    $ ./mkcpsdevinstance --zope-bin=/opt/Zope-2.9/bin /var/opt/cps-3-full-dev  
     66   $ mkcpsdevinstance --zope-bin=/opt/Zope-2.9/bin /var/opt/cps-3-full-dev  
    5467}}} 
     68 
     69Note that the script isn't that robust. You must check obvious things, such as write permission to create the target directory beforehand. 
     70Actually, ```/opt/Zope-2.9/bin``` is the default value, so you can just drop the ```--zope-bin``` option if it is correct in your setup, and in particular if you installed through the Debian package. 
    5571 
    5672The bundle URL for CPS-3-full is just the default value, one can get CPS-3-base by changing it: 
    5773{{{ 
    58    $ ./mkcpsdevinstance -b http://hg.cps-cms.org/CPS/bundles?subpath=CPS-3-base --zope-bin=/opt/Zope-2.9/bin /var/opt/cps-3-base-dev  
     74   $ mkcpsdevinstance -b 'http://hg.cps-cms.org/CPS/bundles?subpath=CPS-3-base' --zope-bin=/opt/Zope-2.9/bin /var/opt/cps-3-base-dev  
    5975}}} 
    6076 
    6177One can use bundle branches as well, or custom bundles: 
    6278{{{ 
    63 ./mkcpsdevinstance -b http://hg.cps-cms.org/CPS/bundles?subpath=CPS-3-full&branch=future-3.5.2 --zope-bin=/opt/Zope-2.9/bin /var/opt/cps-3-future-dev  
    64 ./mkcpsdevinstance -b ssh://me@myproject.example.com/my_bundle --zope-bin=/opt/Zope-2.9/bin /var/opt/myproject-dev 
     79$ mkcpsdevinstance -b 'http://hg.cps-cms.org/CPS/bundles?subpath=CPS-3-full&branch=future-3.5.2' --zope-bin=/opt/Zope-2.9/bin /var/opt/cps-3-future-dev  
     80$ mkcpsdevinstance -b ssh://me@myproject.example.com/my_bundle --zope-bin=/opt/Zope-2.9/bin /var/opt/myproject-dev 
    6581}}} 
    6682 
    67 Note that the ```subpath``` and ```branch``` parameters are specific of this script, they act as modifiers on what is otherwise a regular Mercurial URL. 
     83Note that the ```subpath``` and ```branch``` parameters are specific of this script, they act as modifiers on what is otherwise a regular Mercurial URL.  
     84 
     85Also, the ```branch``` parameter is simply passed as ```-r``` to ```hg update```. Therefore it works also for tags or to pin a revision. For instance, to get a working CPS-3.5.1 (full) rig, just do (assuming the Zope install is in the default place, namely ```/opt/Zope-2.9```): 
     86 
     87{{{ 
     88$ mkcpsdevinstance -b 'http://hg.cps-cms.org/CPS/bundles?branch=3.5.1' /var/opt/cps-3-future-dev  
     89}}} 
    6890 
    6991