The revisions let you track differences between multiple versions of a post.
On 2006-12, I (Dave Allen Barker Jr) installed Drupal for my first time. I had complete access to the host.
This is not an endorsement of these versions, just what I happened to use during this particular installation.
This information does not provide installation instruction on its own—it is meant as a companion to the installation information provided by Drupal and its dependencies.
It is important that we do not grant any more permissions to files and directories than necessary. Because we're working in our user (home) directory, anything we add will have our default user permissions. This may not be enough, but we will grant more as needed.
I made a directory named 620
to put any files (not just Drupal's) this project may need.
Unfortunately, Drupal was not packaged for Debian a the time, so I:
drupal
in the 620
directory and changed to itln -s
) named live
to the unpacked drupal directory (drupal-5.0-beta2
)This last step I did in anticipation of future Drupal upgrades. My thought is that simply changing the live
simlink will allow "pivoting" into a new Drupal version without changing any settings that might depend on its location.
Drupal's INSTALL.txt
file specifies its requirements, of which all were available as Debian packages. This made installation as easy as:
aptitude install mysql-server apache2 php5 php5-mysql php5-gd
Note: The need for php5-mysql
was discovered later when running the install script, and php5-gd
in the "Status report" upon first view of the "Administer" page.
apache2
in my 620
directoryIn my apache2
directory, make a httpd.conf
file containing the following:
NameVirtualHost *
<VirtualHost *>
ServerName domainname
Alias / /home/one/var/620/drupal/live/
<Directory /home/one/var/620/drupal>
AllowOverride Indexes Limit Options=Indexes,FollowSymLinks FileInfo
</Directory>
</VirtualHost>
/etc/apache2/sites-available/620
to homedirectory/620/apache2/httpd.conf
a2ensite 620
) and have Apache re-read its configuration (invoke-rc.d apache2 reload
)Note: The AllowOverride
directive options were added by trial and error by setting the LogLevel
to debug
, accessing the site for the first time (to run the install script), checking the Apache error log (/var/log/apache2/error.log
), and adding appropriate options until the errors were quelled.
Instructions to create Drupal's database in MySQL are provided in Drupal's INSTALL.mysql.txt
file. I chose the following names:
620drupal
620
Note: I began with a database name of 620-drupal
but later learned its dash (-) was the reason why the command to set the access database rights was failing me. I also learned that one way to fix the command in MySQL was to escape the database name with backticks (`620-drupal`
). This made me nervous, and not wanting to trust that all other programs accessing the database would properly escape my dash laden database name, I removed the dash.
The install script (run upon accessing the site for the first time) will need to modify a file that should otherwise not be writeable. From the Drupal directory (620/drupal/live/
):
chmod o+w sites/default/settings.php
(make Drupal's settings file world writable)chmod o-w sites/default/settings.php
(make Drupal's settings file not world writable)files
DirectoryFrom the Drupal default site directory (620/drupal/live/sites/default
) make a directory named files
, where it and new files under it are owned and writable by the www-data
group.
mkdir files
chown :www-data files
chmod g+w files
See the initial configuration notes.
Recent comments
2011, January 26 - 5:04pm
2011, January 13 - 5:48pm
2010, March 12 - 12:53am
2010, March 11 - 9:49pm
2009, November 30 - 3:32pm
2009, November 30 - 3:09pm
2009, November 30 - 1:01pm
2009, November 30 - 10:50am
2009, November 30 - 10:29am
2009, November 29 - 10:15pm