/[drupal]/contributions/modules/testing_server_setup/README.txt
ViewVC logotype

Contents of /contributions/modules/testing_server_setup/README.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.5 - (show annotations) (download)
Thu Jul 9 19:22:46 2009 UTC (4 months, 2 weeks ago) by boombatower
Branch: MAIN
CVS Tags: DRUPAL-6--2-1, HEAD
Changes since 1.4: +8 -1 lines
File MIME type: text/plain
#500454: clarify the steps in PIFR INSTALL.txt that should be peformed.
1 $Id: README.txt,v 1.4 2009/07/09 18:46:50 boombatower Exp $
2
3 TESTING SERVER INSTALL PACKAGE
4
5 OVERVEIW:
6 This package checks all server dependencies, installs the Drupal codebase and
7 supporting testing modules, configures PHP and an Apache virtual host for the
8 website, installs all necessary databases and configures access permissions
9 for Drupal, installs a pre-built version of Drupal, and sets up the environment
10 for testing admins.
11
12 SUPPORTED DISTROS:
13 Distro profiles are in the 'profiles' directory -- any details relevant to the
14 profile will be in the comments at the top of the profile.
15
16 Other distros may work fine with this script, or require some minor editing of
17 the server configuration variables in one of the distro profiles.
18
19 PREREQUISITES:
20 The following must be installed and running before attempting to run the server
21 install script:
22
23 - CVS (client only)
24 - An Apache webserver configured to support a Drupal installation, including
25 a working mod_rewrite.
26 - PHP 5.2 or greater, both the Apache module and CLI.
27 - A supported Drupal 7 database.
28 - A firewall set up according to the installation instructions for the Drupal
29 project_issue_file_review module.
30
31 TO USE:
32 1. Drop 'testing_server_setup.sh' from the testing_server_setup module into
33 /var/local directory on your server.
34 If /var/local doesn't exist, create it and set it's permissions to 755.
35
36 An easy way to do this is:
37 a) change directory to /var
38 cd /var
39
40 b) checkout the testing_server_setup module from CVS
41 cvs -z6 -d :pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal-contrib checkout -d local contributions/modules/testing_server_setup
42
43 To checkout a specific version of the module, use:
44 cvs -z6 -d :pserver:anonymous:anonymous@cvs.drupal.org:/cvs/drupal-contrib checkout -d local -r TAG contributions/modules/testing_server_setup
45 where TAG is the CVS tag required
46
47 c) Set the permissions on /var/local
48 chmod 755 /var/local
49
50
51 2. Execute the following commands:
52 cd /var/local
53 ./testing_server_install.sh
54
55 This will download the rest of the setup files, and set up a default
56 configuration file which you will need to edit according to your server's
57 setup.
58
59 NOTE: Since the config file contains sensitive information about your MySQL
60 server, you should make sure the file is owned by root, and read/write
61 only for root.
62
63 3. The default setup files come with administrator profiles for the currently
64 recommended testing server administrators for drupal.org testing servers.
65 To add more testing administration users, create new files in the 'admins'
66 directory, using the same format as any of the existing admin files. Make
67 sure the name of any file you create matches the admin user's desired login
68 name.
69
70 NOTE: If you wish to restrict the allowed admins for the server, edit the
71 ALLOWED_ADMINS setting in the configuration file to suit your needs.
72
73 4. Re-run the commands in Step 2 to complete the installation.
74
75 5. Ensure that the db information in the settings.php file is correct. Read the
76 INSTALL.txt in the Project issue file review (PIFR) module at step #4 for
77 details.
78
79 6. Perform step #5 of the INSTALL.txt in the Project issue file review (PIFR)
80 module.
81
82 If any of the prerequisite tests fail, correct the issue and re-run the script.
83 If any serious errors occur in the install script, you'll need to contact a
84 testing server administrator to help resolve the issue.

  ViewVC Help
Powered by ViewVC 1.1.2