| 1 |
Elgg version 0.1.2 alpha installation instructions |
|---|
| 2 |
|
|---|
| 3 |
Ben Werdmuller <ben@elgg.net> |
|---|
| 4 |
23rd April, 2005 |
|---|
| 5 |
|
|---|
| 6 |
|
|---|
| 7 |
1. BEFORE YOU BEGIN |
|---|
| 8 |
|
|---|
| 9 |
1.1 Requirements |
|---|
| 10 |
|
|---|
| 11 |
Elgg currently requires the Apache web server with mod_rewrite |
|---|
| 12 |
installed and the ability to send emails, plus PHP 4.3+ and MySQL |
|---|
| 13 |
3.23+. It has currently been tested on Apache installations running |
|---|
| 14 |
Red Hat Linux and Microsoft Windows XP. |
|---|
| 15 |
|
|---|
| 16 |
In your Apache configuration, you must have AllowOverride set to |
|---|
| 17 |
All for the virtual server where Elgg is installed. |
|---|
| 18 |
|
|---|
| 19 |
Elgg must be installed on the root of a domain - for example, |
|---|
| 20 |
at http://elgg.net/, as opposed to http://elgg.net/subdirectory/. |
|---|
| 21 |
|
|---|
| 22 |
You must have a database on the MySQL server ready for use by Elgg. |
|---|
| 23 |
|
|---|
| 24 |
IF YOU ARE UPGRADING FROM 0.1.1a, you do not need to alter the database |
|---|
| 25 |
schema (and can ignore section 3 of these instructions). |
|---|
| 26 |
|
|---|
| 27 |
IF YOU ARE UPGRADING FROM EARLIER VERSIONS, you must drop any existing |
|---|
| 28 |
database tables and insert the new database schema. |
|---|
| 29 |
|
|---|
| 30 |
|
|---|
| 31 |
1.2 Recommendations |
|---|
| 32 |
|
|---|
| 33 |
For this release, it is recommended that MySQL has cacheing enabled. |
|---|
| 34 |
Please see the MySQL documentation for instructions, or ask your |
|---|
| 35 |
system administrator. |
|---|
| 36 |
|
|---|
| 37 |
|
|---|
| 38 |
1.3 Time estimate |
|---|
| 39 |
|
|---|
| 40 |
Assuming you have satisfied the requirements in 1.1, the installation |
|---|
| 41 |
should not take longer than 20 minutes. This may vary depending on |
|---|
| 42 |
the connection speed to your web server. |
|---|
| 43 |
|
|---|
| 44 |
|
|---|
| 45 |
|
|---|
| 46 |
2. INSTALLING FILES |
|---|
| 47 |
|
|---|
| 48 |
|
|---|
| 49 |
2.1 Deploy Elgg framework |
|---|
| 50 |
|
|---|
| 51 |
Move all files aside from README, LICENSE, INSTALL and the |
|---|
| 52 |
"distribution" directory from the distribution package to your web |
|---|
| 53 |
server directory. Files in the root of the distribution must be in |
|---|
| 54 |
the root of your web server account. |
|---|
| 55 |
|
|---|
| 56 |
IF YOU ARE UPGRADING, you may wish to retain your existing |
|---|
| 57 |
includes.php file. |
|---|
| 58 |
|
|---|
| 59 |
|
|---|
| 60 |
2.1 Set permissions on special directories |
|---|
| 61 |
|
|---|
| 62 |
Some directories need to be written to during Elgg's normal operation |
|---|
| 63 |
- specifically the directory for uploaded files, and the directory |
|---|
| 64 |
for uploaded icons. |
|---|
| 65 |
|
|---|
| 66 |
From your root directory, navigate to /_icons. On Linux / Unix, you |
|---|
| 67 |
must change the access privileges for /_icons/data to 777 or |
|---|
| 68 |
equivalent. To do this you may be able to right click on the folder |
|---|
| 69 |
and set the "CHMOD" value, or you may have to use your command line |
|---|
| 70 |
terminal, navigate to the _icons folder, and type: |
|---|
| 71 |
|
|---|
| 72 |
chmod 777 data |
|---|
| 73 |
|
|---|
| 74 |
Repeat this process for /_files/data. |
|---|
| 75 |
|
|---|
| 76 |
|
|---|
| 77 |
|
|---|
| 78 |
3. SETTING UP THE DATABASE |
|---|
| 79 |
|
|---|
| 80 |
|
|---|
| 81 |
3.1 Open database schema |
|---|
| 82 |
|
|---|
| 83 |
There is a database schema supplied in the /distribution/database |
|---|
| 84 |
folder. You must install this into the database you have set aside |
|---|
| 85 |
for elgg. |
|---|
| 86 |
|
|---|
| 87 |
If you are running phpMyAdmin, a third-party tool for easily |
|---|
| 88 |
maintaining MySQL databases, go to 3.2; otherwise go to 3.3. |
|---|
| 89 |
|
|---|
| 90 |
|
|---|
| 91 |
3.2 Setting up the database with phpMyAdmin |
|---|
| 92 |
|
|---|
| 93 |
In phpMyAdmin, click on the database you wish to use for Elgg on the |
|---|
| 94 |
left hand side of the screen. Click on the "SQL" tab at the top of |
|---|
| 95 |
the screen, and on the page that turns up, click "Browse" to pick a |
|---|
| 96 |
textfile to import. Navigate to /distribution/database in the |
|---|
| 97 |
distribution package and select elgg.sql. Click "Go". |
|---|
| 98 |
|
|---|
| 99 |
|
|---|
| 100 |
3.3 Setting up the database with command line MySQL |
|---|
| 101 |
|
|---|
| 102 |
Using your command line terminal, navigate to /distribution/database |
|---|
| 103 |
in the distribution package. Type the following: |
|---|
| 104 |
|
|---|
| 105 |
mysql -u [username] -p [password] [databasename] < elgg.sql |
|---|
| 106 |
|
|---|
| 107 |
Where [username] and [password] are your MySQL access details and |
|---|
| 108 |
[databasename] is the name of the database you have set aside for |
|---|
| 109 |
Elgg. |
|---|
| 110 |
|
|---|
| 111 |
Once you have done this, you should delete the /distribution |
|---|
| 112 |
directory. |
|---|
| 113 |
|
|---|
| 114 |
|
|---|
| 115 |
|
|---|
| 116 |
4. SETTING UP ELGG |
|---|
| 117 |
|
|---|
| 118 |
|
|---|
| 119 |
4.1 Edit includes.php |
|---|
| 120 |
|
|---|
| 121 |
Load "includes.php". There are eight variables that must be |
|---|
| 122 |
set at the top of the file - all of them are important, and they are |
|---|
| 123 |
clearly described within the file. Each of them is of the form: |
|---|
| 124 |
|
|---|
| 125 |
define("name","value"); |
|---|
| 126 |
|
|---|
| 127 |
You must enter your values within the second set of quotation marks. |
|---|
| 128 |
To include a quotation mark within a value (e.g. if you wanted |
|---|
| 129 |
My University's "Elgg" Trial to be your site title), prefix it with |
|---|
| 130 |
a backslash ("\"). |
|---|
| 131 |
|
|---|
| 132 |
|
|---|
| 133 |
4.2 Customise your default homepage |
|---|
| 134 |
|
|---|
| 135 |
We have included a basic default homepage, but you can alter index.php |
|---|
| 136 |
as you wish. If you would like to alter the text but maintain the |
|---|
| 137 |
position within Elgg's flexible templating system, you will need to |
|---|
| 138 |
alter the file /content/mainindex/content_main_index.php. |
|---|
| 139 |
|
|---|
| 140 |
|
|---|
| 141 |
4.3 Log in |
|---|
| 142 |
|
|---|
| 143 |
We have included a default user, "news". This user owns all the |
|---|
| 144 |
public custom templates. Its login name is "news" and its default |
|---|
| 145 |
password is "password"; you should log in and change this as soon |
|---|
| 146 |
as possible. All new users will automatically list the news account |
|---|
| 147 |
as a friend, so you should not delete it. |
|---|
| 148 |
|
|---|
| 149 |
|
|---|
| 150 |
|
|---|
| 151 |
5. FURTHER CUSTOMISATION AND DEVELOPMENTS |
|---|
| 152 |
|
|---|
| 153 |
Please keep an eye on http://elgg.net/development/index.php for |
|---|
| 154 |
forthcoming developments within Elgg, including documentation on how |
|---|
| 155 |
to alter your default templates and writing new functionality into |
|---|
| 156 |
the system. |
|---|