5
2. Manual initial database generation and configuration
6
3. Database population script
7
4. Deleting the Drupal database
8
5. Changes to Apache 2 configuration
9
6. Securing your portal
10
7. Upgrading database from previous versions
12
9. Additional themes and modules
13
10. Privacy of session cookies
16
B. Links for more support
21
The latest version of Drupal can always be found at
22
<http://www.drupal.org>.
24
A running database server is needed for this package to work. It
25
doesn't matter whether the DBMS runs on the same machine as the
26
web server. MySQL and PostgreSQL servers are supported by this package.
28
You can change the DBMS configuration after installation by running
29
"dpkg-reconfigure drupal"
32
2. Manual initial database generation and configuration
33
-------------------------------------------------------
34
This is only necessary if you chose not to automatically create the
35
database at installation time or if automatic creation failed.
37
Directions on how to create a database for you drupal portal can be found
38
in INSTALL.mysql.txt and INSTALL.pgsql.txt files in /usr/share/doc/drupal6.
41
3. Database population script
42
-----------------------------
43
Once a database is set up and configured, drupal needs to create tables and
44
insert default records into it.
46
This can be done running the install.php script on portal web site, e.g.
48
http://localhost/drupal5/install.php
51
4. Deleting the Drupal database
52
-------------------------------
53
The database may be deleted automatically on purging the package
54
(debconf prompt the user asking to do it or not).
56
If you want to purge the data stored at MySQl database manually you
57
can use the following command:
59
'mysqladmin -p drop drupal6'
61
being the user who admin MySQL.
64
5. Changes to Apache 2 configuration
65
------------------------------------
67
By default, Drupal passes path arguments to itself via its dynamically
68
generated URLs. This results in URLs that look like
69
"http://www.example.com/?q=node/83." This can make URLs hard to read and it
70
prevents some search engines from indexing the pages with these URLs
72
You can tell Drupal to use "clean URLs", eliminating the "?q=" in internal
73
URLs, simply enabling mod_rewrite in apache 2 configuration (a2enmod rewrite).
74
Please note that you may need to adjust the /etc/drupal/6/htaccess
75
configuration file to match your site configuration.
78
6. Securing your portal
79
-----------------------
80
It is very good security measure to restrict access to admin.php only
81
to trusted IP's and localhost (you can see an example at
82
/etc/drupal/6/htaccess) As an added security measure, is a good idea to
83
set up a ssl-enabled web server in your apache, and allow access to
84
admin page only to ssl streams.
87
7. Upgrading database from previous versions
88
--------------------------------------------
89
From version 4.7.4 drupal packages will be separated for each major version.
90
Automatic upgrading the database will not be attempted anymore.
92
To upgrade an existing version of drupal, install the new package and manually
93
configure the database to point to the existing database, then execute the
94
upstream upgrade script by pointing a web browser to
96
<http://$SITE/update.php>
98
Then remove the old package.
100
WARNING: be sure to _NOT_ remove the old package's database.
105
Drupal supports a setup with multiple virtual hosts. Each virtual host
106
has its own configuration directory in /etc/drupal/6/sites/_virtualhost_.
107
At install time the 'default' virtual host is created with the required
108
settings.php configuration file.
110
To create new virtual hosts simply duplicate the default virtual host directory
111
and adjust the settings.php and dbconfig.php configuration files.
113
This package supports running cron scripts on each virtual host, as long as you
114
define the $base_url variable in the virtual host settings.php configuration
118
9. Additional modules and themes
119
--------------------------------
121
Drupal looks for modules and themes in the modules/ and themes/
122
subdirectories, respectively. However, it would be a bad idea to put
123
additional modules and themes into those directories because they
124
might be overwritten on upgrades. Instead, create links to another
125
directory that won't be touched by dpkg, e.g. in the /usr/local
128
# ln -s /usr/local/share/drupal/modules /usr/share/drupal6/modules/local
129
# ln -s /usr/local/share/drupal/themes /usr/share/drupal6/themes/local
132
10. Privacy of session cookies
133
------------------------------
135
Drupal does not set the secure flag for the session cookie in an https
136
session, which can cause the cookie to be sent in http requests and make
137
it easier for remote attackers to capture this cookie.
139
If you are using drupal on an https connection you can fix this issue
140
setting the session.cookie_secure PHP properties to on either in the
141
global PHP configuration file or adding the following line to
142
/etc/drupal/6/htaccess:
144
php_value session.cookie_secure 1
147
A. Customizing themes
148
---------------------
149
To create or customize a theme for your site, I recommend to start
150
with an existing theme (as exmaple), copy it to a different location
152
# cp -ai /etc/drupal/6/themes/example /etc/drupal/6/themes/Custom
154
and modify this new created theme. You can now select your "Custom"
155
theme in the Preferences menu from the admin interface.
157
You should not modify and use an included theme in the package
158
directly, as your changes could be overwritten next time you upgrade
162
B. Links for more support
163
-------------------------
164
* http://www.drupal.org/
165
- Drupal's project page for those willing to get involved in the
168
* http://www.drupal.org/node.php?id=253
169
- online installation guidelines
171
-- Luigi Gangitano <luigi@debian.org> Mon, 11 Aug 2008 12:00:12 +0100
added
removed
debian/README.Debian
