manuelcillero/suitedesk
manuelcillero/suitedesk
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Preparing install and configuration documents

Browse source
This commit is contained in:
Manuel Cillero 2017-08-09 19:16:27 +02:00
parent dfa2e142a7
commit 1475bac9a8
4 changed files with 121 additions and 556 deletions
Download patch file Download diff file Expand all files Collapse all files

233
config/default/default.settings.php
View file

@ -1,79 +1,70 @@
<?php
/**
* @file
* Drupal site-specific configuration file.
* SuiteDesk site-specific configuration file.
*
* IMPORTANT NOTE:
* This file may have been set to read-only by the Drupal installation
* program. If you make changes to this file, be sure to protect it again
* after making your modifications. Failure to remove write permissions
* to this file is a security risk.
* This file may have been set to read-only by Drupal. If you make changes to
* this file, be sure to protect it again after making your modifications.
* Failure to remove write permission to this file is a security risk.
*
* The configuration file to be loaded is based upon the rules below.
*
* The configuration directory will be discovered by stripping the
* website's hostname from left to right and pathname from right to
* left. The first configuration file found will be used and any
* others will be ignored. If no other configuration file is found
* then the default configuration file at 'config/default' will be used.
* The configuration directory will be discovered by stripping the website's
* hostname from left to right and pathname from right to left. The first
* configuration file found will be used and any others will be ignored. If no
* other configuration file is found then the default configuration file at
* 'config/default' will be used. For example, for a fictitious site installed
* at http://www.example.org/mysite/test the 'settings.php' is searched in the
* following directories:
*
* For example, for a fictitious site installed at
* http://www.drupal.org/mysite/test/, the 'settings.php'
* is searched in the following directories:
*
* 1. config/www.drupal.org.mysite.test
* 2. config/drupal.org.mysite.test
* 1. config/www.example.org.mysite.test
* 2. config/example.org.mysite.test
* 3. config/org.mysite.test
*
* 4. config/www.drupal.org.mysite
* 5. config/drupal.org.mysite
* 4. config/www.example.org.mysite
* 5. config/example.org.mysite
* 6. config/org.mysite
*
* 7. config/www.drupal.org
* 8. config/drupal.org
* 7. config/www.example.org
* 8. config/example.org
* 9. config/org
*
* 10. config/default
*
* If you are installing on a non-standard port number, prefix the
* hostname with that number. For example,
* http://www.drupal.org:8080/mysite/test/ could be loaded from
* config/8080.www.drupal.org.mysite.test/.
* If you are installing on a non-standard port number, prefix the hostname with
* that number. For example, http://www.example.org:8080/mysite/test could be
* loaded from config/8080.www.drupal.org.mysite.test directory.
*/
/**
* Database settings:
* Database settings.
*
* Note that the $db_url variable gets parsed using PHP's built-in
* URL parser (i.e. using the "parse_url()" function) so make sure
* not to confuse the parser. If your username, password
* or database name contain characters used to delineate
* $db_url parts, you can escape them via URI hex encodings:
* Note that the $db_url variable gets parsed using PHP's built-in URL parser
* (i.e. using the "parse_url()" function) so make sure not to confuse the
* parser. If your username, password or database name contain characters used
* to delineate $db_url parts, you can escape them via URI hex encodings:
*
* : = %3a / = %2f @ = %40
* + = %2b ( = %28 ) = %29
* ? = %3f = = %3d & = %26
*
* To specify multiple connections to be used in your site (i.e. for
* complex custom modules) you can also specify an associative array
* of $db_url variables with the 'default' element used until otherwise
* requested.
* To specify multiple connections to use in your site (i.e. for complex custom
* modules) you can also specify an associative array of $db_url variables with
* the 'default' element used until otherwise requested.
*
* You can optionally set prefixes for some or all database table names
* by using the $db_prefix setting. If a prefix is specified, the table
* name will be prepended with its value. Be sure to use valid database
* characters only, usually alphanumeric and underscore. If no prefixes
* are desired, leave it as an empty string ''.
* If you prefix some or all database table names, you can use the $db_prefix
* setting and each table name will be prepended with its value. Be sure to use
* valid database characters only, usually alphanumeric and underscore. If no
* prefixes are desired, leave it as an empty string ''.
*
* To have all database names prefixed, set $db_prefix as a string:
*
* $db_prefix = 'main_';
*
* To provide prefixes for specific tables, set $db_prefix as an array.
* The array's keys are the table names and the values are the prefixes.
* The 'default' element holds the prefix for any tables not specified
* elsewhere in the array. Example:
* To provide prefixes for specific tables set $db_prefix as an array where keys
* are the table names and the values are the prefixes. The 'default' element
* holds the prefix for any tables not specified elsewhere in the array:
*
* $db_prefix = array(
* 'default' => 'main_',
@ -91,6 +82,15 @@
$db_url = 'mysql://username:password@localhost/databasename';
$db_prefix = '';
/**
* SuiteCRM (a fork of SugarCRM) access.
*
* Don't forget to assign TRUE to this variable and uncomment to provide the
* SuiteCRM database connection.
*/
$conf['storm_suitecrm'] = FALSE;
# $db_url['sugarcrm'] = 'mysql://username:password@localhost/databasename';
/**
* Database default collation.
*
@ -100,37 +100,36 @@ $db_prefix = '';
* for many use-cases, but depending on the language(s) of the stored data, it
* may be necessary to use a different collation.
* Important:
* - Only set or change this value BEFORE installing Drupal, unless you know
* - Only set or change this value BEFORE installing SuiteDesk, unless you know
* what you are doing.
* - All database tables and columns should be in the same collation. Otherwise,
* string comparisons performed for table JOINs will be significantly slower.
* - Especially when storing data in German or Russian on MySQL 5.1+, you want
* to use the 'utf8_unicode_ci' collation instead.
*
* @see http://drupal.org/node/772678
* - More information at http://drupal.org/node/772678
*/
# $db_collation = 'utf8_general_ci';
/**
* Access control for update.php script
* Access control for update.php script.
*
* If you are updating your Drupal installation using the update.php script
* If you are updating your SuiteDesk installation using the update.php script
* being not logged in as administrator, you will need to modify the access
* check statement below. Change the FALSE to a TRUE to disable the access
* check. After finishing the upgrade, be sure to open this file again
* and change the TRUE back to a FALSE!
* check statement below. Change the FALSE to a TRUE value to disable the access
* check. After finishing the upgrade, be sure to open this file again and
* change the TRUE back to a FALSE!
*/
$update_free_access = FALSE;
/**
* Base URL (optional).
*
* If you are experiencing issues with different site domains,
* uncomment the Base URL statement below (remove the leading hash sign)
* and fill in the absolute URL to your Drupal installation.
* If you are experiencing issues with different site domains, uncomment the
* Base URL statement below and fill in the absolute URL to your SuiteDesk
* installation.
*
* You might also want to force users to use a given domain.
* See the .htaccess file for more information.
* You might also want to force users to use a given domain. See the .htaccess
* file for more information.
*
* Examples:
* $base_url = 'http://www.example.com';
@ -138,71 +137,67 @@ $update_free_access = FALSE;
* $base_url = 'http://www.example.com/drupal';
* $base_url = 'https://www.example.com:8888/drupal';
*
* It is not allowed to have a trailing slash; Drupal will add it
* for you.
* It is not allowed to have a trailing slash; Drupal will add it for you.
*/
# $base_url = 'http://www.example.com'; // NO trailing slash!
/**
* PHP settings:
* PHP settings.
*
* To see what PHP settings are possible, including whether they can
* be set at runtime (ie., when ini_set() occurs), read the PHP
* documentation at http://www.php.net/manual/en/ini.php#ini.list
* and take a look at the .htaccess file to see which non-runtime
* settings are used there. Settings defined here should not be
* duplicated there so as to avoid conflict issues.
* To see what PHP settings are possible, including whether they can be set at
* runtime (i.e., when ini_set() occurs), read the PHP documentation at
* http://www.php.net/manual/en/ini.php#ini.list and take a look at the
* .htaccess file to see which non-runtime settings are used there. Settings
* defined here should not be duplicated there so as to avoid conflict issues.
*/
ini_set('arg_separator.output', '&amp;');
ini_set('magic_quotes_runtime', 0);
ini_set('magic_quotes_sybase', 0);
ini_set('session.cache_expire', 200000);
ini_set('session.cache_limiter', 'none');
ini_set('session.cookie_lifetime', 2000000);
ini_set('session.gc_maxlifetime', 200000);
ini_set('session.cache_expire', 259200); // 72 horas
ini_set('session.cache_limiter', 'none'); // ¿nocache?
ini_set('session.cookie_lifetime', 2592000); // 30 días
ini_set('session.gc_maxlifetime', 259200); // 72 horas
ini_set('session.save_handler', 'user');
ini_set('session.use_cookies', 1);
ini_set('session.use_only_cookies', 1);
ini_set('session.use_trans_sid', 0);
ini_set('url_rewriter.tags', '');
# ini_set('memory_limit', '140M');
/**
* If you encounter a situation where users post a large amount of text, and
* the result is stripped out upon viewing but can still be edited, Drupal's
* output filter may not have sufficient memory to process it. If you
* experience this issue, you may wish to uncomment the following two lines
* and increase the limits of these variables. For more information, see
* http://php.net/manual/en/pcre.configuration.php.
* If you encounter a situation where users post a large amount of text, and the
* result is stripped out upon viewing but can still be edited, Drupal's output
* filter may not have sufficient memory to process it. If you experience this
* issue, you may wish to uncomment the following two lines and increase their
* limit values. See http://php.net/manual/en/pcre.configuration.php.
*/
# ini_set('pcre.backtrack_limit', 200000);
# ini_set('pcre.recursion_limit', 200000);
/**
* Drupal automatically generates a unique session cookie name for each site
* based on on its full domain name. If you have multiple domains pointing at
* the same Drupal site, you can either redirect them all to a single domain
* (see comment in .htaccess), or uncomment the line below and specify their
* shared base domain. Doing so assures that users remain logged in as they
* cross between your various domains.
* based on its full domain name. If you have multiple domains pointing at the
* same site, you can either redirect them all to a single domain (see comment
* in .htaccess), or uncomment the line below and specify their shared base
* domain. Doing so assures that users remain logged in as they cross between
* your various domains.
*/
# $cookie_domain = 'example.com';
/**
* Variable overrides:
* Variable overrides.
*
* To override specific entries in the 'variable' table for this site,
* set them here. You usually don't need to use this feature. This is
* useful in a configuration file for a vhost or directory, rather than
* the default settings.php. Any configuration setting from the 'variable'
* table can be given a new value. Note that any values you provide in
* these variable overrides will not be modifiable from the Drupal
* administration interface.
* To override specific entries in the 'variable' table for this site, set
* them here. You usually don't need to use this feature. This is useful in a
* configuration file for a vhost or directory, rather than the default
* settings.php. Any configuration setting from the 'variable' table can be
* given a new value. Note that any values you provide in these variable
* overrides will not be modifiable from the Drupal administration interface.
*
* Remove the leading hash signs to enable.
*/
# $conf = array(
# 'site_name' => 'My Drupal site',
# 'theme_default' => 'garland',
# 'site_name' => 'My SuiteDesk site',
# 'anonymous' => 'Visitor',
/**
* A custom theme can be set for the off-line page. This applies when the site
@ -216,39 +211,39 @@ ini_set('url_rewriter.tags', '');
/**
* reverse_proxy accepts a boolean value.
*
* Enable this setting to determine the correct IP address of the remote
* client by examining information stored in the X-Forwarded-For headers.
* Enable this setting to determine the correct IP address of the remote client
* by examining information stored in the X-Forwarded-For headers.
* X-Forwarded-For headers are a standard mechanism for identifying client
* systems connecting through a reverse proxy server, such as Squid or
* Pound. Reverse proxy servers are often used to enhance the performance
* of heavily visited sites and may also provide other site caching,
* security or encryption benefits. If this Drupal installation operates
* behind a reverse proxy, this setting should be enabled so that correct
* IP address information is captured in Drupal's session management,
* logging, statistics and access management systems; if you are unsure
* about this setting, do not have a reverse proxy, or Drupal operates in
* a shared hosting environment, this setting should be set to disabled.
* systems connecting through a reverse proxy server, such as Squid or Pount.
* Reverse proxy servers are often used to enhance the performance of heavily
* visited sites and may also provide other site caching, security or encryption
* benefits. If this Drupal installation operates behind a reverse proxy, this
* setting should be enabled so that correct IP address information is captured
* in Drupal's session management, logging, statistics and access management
* systems; if you are unsure about this setting, do not have a reverse proxy,
* or Drupal operates in a shared hosting environment, this setting should be
* to disabled.
*/
# 'reverse_proxy' => TRUE,
/**
* reverse_proxy accepts an array of IP addresses.
*
* Each element of this array is the IP address of any of your reverse
* proxies. Filling this array Drupal will trust the information stored
* in the X-Forwarded-For headers only if Remote IP address is one of
* these, that is the request reaches the web server from one of your
* reverse proxies. Otherwise, the client could directly connect to
* your web server spoofing the X-Forwarded-For headers.
* Each element of this array is the IP address of any of your reverse proxies.
* Filling this array Drupal will trust the information stored in the
* X-Forwarded-For headers only if Remote IP address is one of these, that is
* the request reaches the web server from one of your reverse proxies.
* Otherwise, the client could directly connect to your web server spoofing the
* X-Forwarded-For headers.
*/
# 'reverse_proxy_addresses' => array('a.b.c.d', ...),
# );
/**
* String overrides:
* String overrides.
*
* To override specific strings on your site with or without enabling locale
* module, add an entry to this list. This functionality allows you to change
* a small number of your site's default English language interface strings.
* module, add an entry to this list. This functionality allows you to change a
* small number of your site's default English language interface strings.
*
* Remove the leading hash signs to enable.
*/
@ -258,7 +253,7 @@ ini_set('url_rewriter.tags', '');
# );
/**
* Multilingual settings
* Multilingual settings.
*
* This is a collection of variables that can be set up for each language when
* i18n is enabled. These are the basic ones for Drupal core, but you can add
@ -297,3 +292,17 @@ $conf['i18n_variables'] = array(
'watcher_notifications_templates_body_cmt',
'watcher_notifications_templates_body_confirm',
);
/**
* Secure Pages deactivation.
*
* Uncomment to deactivate the secure pages SSL module.
*/
# $conf['securepages_enable'] = 0;
/**
* Advanced CSS/JS Aggregation deactivation.
*
* Uncomment to deactivate the advanced CSS and JS aggregation module.
*/
# $conf['advagg_enabled'] = 0;

30
install/COPYRIGHT.txt
View file

@ -1,30 +0,0 @@
All Drupal code is Copyright 2001 - 2012 by the original authors.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.
You should have received a copy of the GNU General Public License
along with this program as the file LICENSE.txt; if not, please see
http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt.
Drupal is a registered trademark of Dries Buytaert.
Drupal includes works under other copyright notices and distributed
according to the terms of the GNU General Public License or a compatible
license, including:
Javascript
Farbtastic - Copyright (c) 2007 Matt Farina
jQuery - Copyright (c) 2008 John Resig
jQuery Form - Copyright (c) 2007 Mike Alsup
CKEditor - Copyright (c) 2003-2016, CKSource - Frederico Knabben

39
install/INSTALL.mysql.txt
View file

@ -1,39 +0,0 @@
CREATE THE MySQL DATABASE
--------------------------
This step is only necessary if you don't already have a database set-up (e.g. by
your host). In the following examples, 'username' is an example MySQL user which
has the CREATE and GRANT privileges. Use the appropriate user name for your
system.
First, you must create a new database for your Drupal site (here, 'databasename'
is the name of the new database):
mysqladmin -u username -p create databasename
MySQL will prompt for the 'username' database password and then create the
initial database files. Next you must login and set the access database rights:
mysql -u username -p
Again, you will be asked for the 'username' database password. At the MySQL
prompt, enter following command:
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER,
CREATE TEMPORARY TABLES ON databasename.*
TO 'username'@'localhost' IDENTIFIED BY 'password';
where
'databasename' is the name of your database
'username@localhost' is the username of your MySQL account
'password' is the password required for that username
Note: Unless your database user has all of the privileges listed above, you will
not be able to run Drupal.
If successful, MySQL will reply with:
Query OK, 0 rows affected

375
install/INSTALL.txt
View file

@ -1,375 +0,0 @@
CONTENTS OF THIS FILE
---------------------
* Requirements
* Optional requirements
* Installation
* Drupal administration
* Customizing your theme(s)
* Multisite Configuration
* More Information
REQUIREMENTS
------------
SuiteDesk requires a web server, Apache web server is recommended, PHP 5 (better
with version 5.4.45) and MySQL (4.1.1 or greater).
See http://www.php.net and http://www.mysql.com for more information.
OPTIONAL TASKS
--------------
- To use XML-based services such as the Blogger API and RSS syndication,
you will need PHP's XML extension. This extension is enabled by default.
- To use Drupal's "Clean URLs" feature on an Apache web server, you will need
the mod_rewrite module and the ability to use local .htaccess files. For
Clean URLs support on IIS, see "Using Clean URLs with IIS"
(http://drupal.org/node/3854) in the Drupal handbook.
- Various Drupal features require that the web server process (for
example, httpd) be able to initiate outbound connections. This is usually
possible, but some hosting providers or server configurations forbid such
connections. The features that depend on this functionality include the
integrated "Update status" module (which downloads information about
available updates of Drupal core and any installed contributed modules and
themes), the ability to log in via OpenID, fetching aggregator feeds, or
other network-dependent services.
INSTALLATION
------------
1. DOWNLOAD DRUPAL AND OPTIONALLY A TRANSLATION
You can obtain the latest Drupal release from http://drupal.org/. The files
are in .tar.gz format and can be extracted using most compression tools. On a
typical Unix command line, use:
wget http://drupal.org/files/projects/drupal-x.x.tar.gz
tar -zxvf drupal-x.x.tar.gz
This will create a new directory drupal-x.x/ containing all Drupal files
and directories. Move the contents of that directory into a directory within
your web server's document root or your public HTML directory:
mv drupal-x.x/* drupal-x.x/.htaccess /var/www/html
If you would like to have the default English interface translated to a
different language, we have good news. You can install and use Drupal in
other languages from the start. Check whether a released package of the
language desired is available for this Drupal version at
http://localize.drupal.org and download the package. Extract
the contents to the same directory where you extracted Drupal into.
2. CREATE THE CONFIGURATION FILE AND GRANT WRITE PERMISSIONS
Drupal comes with a default.settings.php file in the config/default
directory. The installer uses this file as a template to create your
settings file using the details you provide through the install process.
To avoid problems when upgrading, Drupal is not packaged with an actual
settings file. You must create a file named settings.php. You may do so
by making a copy of default.settings.php (or create an empty file with
this name in the same directory). For example, (from the installation
directory) make a copy of the default.settings.php file with the command:
cp config/default/default.settings.php config/default/settings.php
Next, give the web server write privileges to the config/default/settings.php
file with the command (from the installation directory):
chmod o+w config/default/settings.php
So that the files directory can be created automatically, give the web server
write privileges to the config/default directory with the command (from the
installation directory):
chmod o+w config/default
3. CREATE THE DRUPAL DATABASE
Drupal requires access to a database in order to be installed. Your database
user will need sufficient privileges to run Drupal. Additional information
about privileges, and instructions to create a database using the command
line are available in INSTALL.mysql.txt (for MySQL) or INSTALL.pgsql.txt
(for PostgreSQL).
To create a database using PHPMyAdmin or a web-based control panel consult
the documentation or ask your webhost service provider.
Take note of the username, password, database name and hostname as you
create the database. You will enter these items in the install script.
This step is only necessary if you don't already have a database set-up (e.g. by
your host). In the following examples, 'username' is an example MySQL user which
has the CREATE and GRANT privileges. Use the appropriate user name for your
system.
First, you must create a new database for your Drupal site (here, 'databasename'
is the name of the new database):
mysqladmin -u username -p create databasename
MySQL will prompt for the 'username' database password and then create the
initial database files. Next you must login and set the access database rights:
mysql -u username -p
Again, you will be asked for the 'username' database password. At the MySQL
prompt, enter following command:
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER,
CREATE TEMPORARY TABLES ON databasename.*
TO 'username'@'localhost' IDENTIFIED BY 'password';
where
'databasename' is the name of your database
'username@localhost' is the username of your MySQL account
'password' is the password required for that username
Note: Unless your database user has all of the privileges listed above, you will
not be able to run Drupal.
If successful, MySQL will reply with:
Query OK, 0 rows affected
4. RUN THE INSTALL SCRIPT
To run the install script point your browser to the base URL of your website
(e.g., http://www.example.com).
You will be guided through several screens to set up the database,
create tables, add the first user account and provide basic web
site settings.
The install script will attempt to create a files storage directory
in the default location at config/default/files (the location of the
files directory may be changed after Drupal is installed). In some
cases, you may need to create the directory and modify its permissions
manually. Use the following commands (from the installation directory)
to create the files directory and grant the web server write privileges to it:
mkdir config/default/files
chmod o+w config/default/files
The install script will attempt to write-protect the settings.php file and
the config/default directory after saving your configuration. However, you
may need to manually write-protect them using the commands (from the
installation directory):
chmod a-w config/default/settings.php
chmod a-w config/default
If you make manual changes to the file later, be sure to protect it again
after making your modifications. Failure to remove write permissions to that
file is a security risk. Although the default location for the settings.php
file is at config/default/settings.php, it may be in another location
if you use the multi-site setup, as explained below.
5. CONFIGURE DRUPAL
When the install script succeeds, you will be directed to the "Welcome"
page, and you will be logged in as the administrator already. Proceed with
the initial configuration steps suggested on the "Welcome" page.
If the default Drupal theme is not displaying properly and links on the page
result in "Page Not Found" errors, try manually setting the $base_url variable
in the settings.php file if not already set. It's currently known that servers
running FastCGI can run into problems if the $base_url variable is left
commented out (see http://bugs.php.net/bug.php?id=19656).
6. REVIEW FILE SYSTEM STORAGE SETTINGS AND FILE PERMISSIONS
The files directory created in step 4 is the default file system path used
to store all uploaded files, as well as some temporary files created by Drupal.
After installation, the settings for the file system path may be modified
to store uploaded files in a different location.
It is not necessary to modify this path, but you may wish to change it if:
* your site runs multiple Drupal installations from a single codebase
(modify the file system path of each installation to a different
directory so that uploads do not overlap between installations); or,
* your site runs a number of web server front-ends behind a load
balancer or reverse proxy (modify the file system path on each
server to point to a shared file repository).
To modify the file system path:
* Ensure that the new location for the path exists or create it if
necessary. To create a new directory named uploads, for example,
use the following command from a shell or system prompt (while in
the installation directory):
mkdir uploads
* Ensure that the new location for the path is writable by the web
server process. To grant write permissions for a directory named
uploads, you may need to use the following command from a shell
or system prompt (while in the installation directory):
chmod o+w uploads
* Access the file system path settings in Drupal by selecting these
menu items from the Navigation menu:
Administer > Site configuration > File system
Enter the path to the new location (e.g.: uploads) at the File
System Path prompt.
Changing the file system path after files have been uploaded may cause
unexpected problems on an existing site. If you modify the file system path
on an existing site, remember to copy all files from the original location
to the new location.
Some administrators suggest making the documentation files, especially
CHANGELOG.txt, non-readable so that the exact version of Drupal you are
running is slightly more difficult to determine. If you wish to implement
this optional security measure, use the following command from a shell or
system prompt (while in the installation directory):
chmod a-r CHANGELOG.txt
Note that the example only affects CHANGELOG.txt. To completely hide
all documentation files from public view, repeat this command for each of
the Drupal documentation files in the installation directory, substituting the
name of each file for CHANGELOG.txt in the example.
For more information on setting file permissions, see "Modifying Linux, Unix,
and Mac file permissions" (http://drupal.org/node/202483) or "Modifying
Windows file permissions" (http://drupal.org/node/202491) in the online
handbook.
7. CRON MAINTENANCE TASKS
Many Drupal modules have periodic tasks that must be triggered by a cron
maintenance task, including search module (to build and update the index
used for keyword searching), aggregator module (to retrieve feeds from other
sites), ping module (to notify other sites about new or updated content), and
system module (to perform routine maintenance and pruning on system tables).
To activate these tasks, call the cron page by visiting
http://www.example.com/cron.php, which, in turn, executes tasks on behalf
of installed modules.
Most systems support the crontab utility for scheduling tasks like this. The
following example crontab line will activate the cron tasks automatically on
the hour:
0 * * * * wget -O - -q -t 1 http://www.example.com/cron.php
More information about cron maintenance tasks are available in the help pages
and in Drupal's online handbook at http://drupal.org/cron. Example scripts can
be found in the scripts/ directory.
DRUPAL ADMINISTRATION
---------------------
A new installation of Drupal defaults to a very basic configuration with only a
few active modules and minimal user access rights.
Use your administration panel to enable and configure services. For example:
General Settings Administer > Site configuration > Site information
Enable Modules Administer > Site building > Modules
Configure Themes Administer > Site building > Themes
Set User Permissions Administer > User management > Permissions
For more information on configuration options, read the instructions which
accompany the different configuration settings and consult the various help
pages available in the administration panel.
Community-contributed modules and themes are available at http://drupal.org/.
CUSTOMIZING YOUR THEME(S)
-------------------------
Now that your installation is running, you will want to customize the look of
your site. Several sample themes are included and more can be downloaded from
drupal.org.
Simple customization of your theme can be done using only CSS. Further changes
require understanding the phptemplate engine that is part of Drupal. See
http://drupal.org/handbook/customization to find out more.
MULTISITE CONFIGURATION
-----------------------
A single Drupal installation can host several Drupal-powered sites, each with
its own individual configuration.
Additional site configurations are created in subdirectories within the 'config'
directory. Each subdirectory must have a 'settings.php' file which specifies the
configuration settings. The easiest way to create additional sites is to copy
the 'default' directory and modify the 'settings.php' file as appropriate. The
new directory name is constructed from the site's URL. The configuration for
www.example.com could be in 'config/example.com/settings.php' (note that 'www.'
should be omitted if users can access your site at http://example.com/).
Sites do not have to have a different domain. You can also use subdomains and
subdirectories for Drupal sites. For example, example.com, sub.example.com,
and sub.example.com/site3 can all be defined as independent Drupal sites. The
setup for a configuration such as this would look like the following:
config/default/settings.php
config/example.com/settings.php
config/sub.example.com/settings.php
config/sub.example.com.site3/settings.php
When searching for a site configuration (for example www.sub.example.com/site3),
Drupal will search for configuration files in the following order, using the
first configuration it finds:
config/www.sub.example.com.site3/settings.php
config/sub.example.com.site3/settings.php
config/example.com.site3/settings.php
config/www.sub.example.com/settings.php
config/sub.example.com/settings.php
config/example.com/settings.php
config/default/settings.php
If you are installing on a non-standard port, the port number is treated as the
deepest subdomain. For example: http://www.example.com:8080/ could be loaded
from config/8080.www.example.com/. The port number will be removed according to
the pattern above if no port-specific configuration is found, just like a real
subdomain.
Each site configuration can have its own site-specific modules and themes in
addition to those installed in the standard 'modules' and 'themes' directories.
To use site-specific modules or themes, simply create a 'modules' or 'themes'
directory within the site configuration directory. For example, if
sub.example.com has a custom theme and a custom module that should not be
accessible to other sites, the setup would look like this:
config/sub.example.com/:
settings.php
themes/custom_theme
modules/custom_module
NOTE: for more information about multiple virtual hosts or the configuration
settings, consult the Drupal handbook at drupal.org.
For more information on configuring Drupal's file system path in a multi-site
configuration, see step 6 above.
MORE INFORMATION
----------------
- For additional documentation, see the online Drupal handbook at
http://drupal.org/handbook.
- For a list of security announcements, see the "Security announcements" page
at http://drupal.org/security (available as an RSS feed). This page also
describes how to subscribe to these announcements via e-mail.
- For information about the Drupal security process, or to find out how to report
a potential security issue to the Drupal security team, see the "Security team"
page at http://drupal.org/security-team.
- For information about the wide range of available support options, see the
"Support" page at http://drupal.org/support.