root/trunk/midgard/tools/midrepository/INSTALL

Revision 7101, 2.9 kB (checked in by bergius, 5 years ago)

Initial commit of the MidRepository? workflow extension
Issue number:
Obtained from:
Submitted by:
Reviewed by:

  • Property svn:eol-style set to native
  • Property svn:executable set to *
  • Property svn:keywords set to Author Date Id Revision
Line 
1 MidRepository installation
2 **************************
3 Copyright (C) 2003 David Schmitter, Dataflow Solutions GmbH <schmitt@dataflow.ch>
4
5 The install scripts are borrowed from the data package.
6
7 If you care about your data, BACK IT UP!
8
9
10 Dependencies
11 ------------
12 PHP 4.2.3 with command line support, should work with 4.3 with minor modifications
13 PHP extensions: domxml, curl, mysql.
14 atd which apache user may use (modify /etc/at.deny or similar)
15 CVS >= 1.11
16 Midgard from CVS --with-multilang --with-vc --with-repligard-enhance --with-page-owner --with-cache-fix
17
18 Preparations
19 ------------
20 * /var/mgd or whatever base directory configured needs to be added to your include_path in php.ini. Setting max_execution_time = 0, memory_limit = 256M is also recommended. If you have a separate php.ini for the CGI version you need to include it there too.
21
22 * If your php commandline interpreter is not located at /usr/bin/php4 you need to make a symlink to that location.
23
24 *** Choose between ***
25
26 New install
27 -----------
28 * Installs a fresh staging / live setup with current oldadmin + asgard, borrowed from the data package. I also made a similar package based on Aegir but I don't distribute it because of possible license problems.
29
30 * Run ./configure --with-host=your.host.name --with-ip=1.2.3.4 etc. (see ./configure --help)
31
32 * Run ./dbinstall. This will generate 5 databases: frontend staging, backend staging, frontend live, backend live, meta and scripts in /var/mgd (default)
33
34 * If you have already run ./dbinstall you first need to run ./clear to wipe the remnants, otherwise ./dbinstall won't work. This wipes all databases, blobs etc. configured, so back up if there is any real data.
35
36 * The generated midgard-workflow.conf needs to be included or merged into your apache config.
37
38 * Restart apache and run /var/mgd/everymin.php from the command line. If there is no error message, it probably works, and you can verify the everymin.php entry in your /etc/crontab and restart cron.
39
40 *** Or ****
41
42 Convert your existing DB
43 ------------------------
44 * Uses an existing DB and tries to convert it into a staging / live setup (everything published initially). It does this without overwriting the original DB. It can take an hour or longer if you have a lot of data. You can't convert a staging / live setup yet.
45
46 * Run configure with --with-install=convert --with-convert-db=dbname (the original db). The blobs that belong to your existing db need to be in $blobroot/blobs_$dbname (adjust --with-blobroot)
47
48 * Continue as above.
49
50
51 Try it out
52 ----------
53 Log in to the control interface at http://host:staging-port(default 8001)/vccontrol?path=/sitegroup:SG0/page:Asgard_Root (for example).
54
55 Try http://host:staging-port(default 8001)/vc/create to create a test sitegroup. If the page is mostly green, it works :)
56
57
58 Oh well
59 -------
60 It's not tested on a lot of different setups and probably won't work without tweaking. Report your problems, please.
Note: See TracBrowser for help on using the browser.