Rename sites directory to be the new config repository
This commit is contained in:
parent
006992b900
commit
433e7eec80
31 changed files with 196 additions and 216 deletions
|
|
@ -13,19 +13,10 @@ CONTENTS OF THIS FILE
|
|||
REQUIREMENTS
|
||||
------------
|
||||
|
||||
Drupal requires a web server, PHP 4 (4.3.5 or greater) or PHP 5
|
||||
(http://www.php.net/) and either MySQL (http://www.mysql.com/) or PostgreSQL
|
||||
(http://www.postgresql.org/). The Apache web server and MySQL database are
|
||||
recommended; other web server and database combinations such as IIS and
|
||||
PostgreSQL have been tested to a lesser extent. When using MySQL, version 4.1.1
|
||||
or greater is recommended to assure you can safely transfer the database.
|
||||
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).
|
||||
|
||||
For more detailed information about Drupal requirements, see "Requirements"
|
||||
(http://drupal.org/requirements) in the Drupal handbook.
|
||||
|
||||
For detailed information on how to configure a test server environment using
|
||||
a variety of operating systems and web servers, see "Local server setup"
|
||||
(http://drupal.org/node/157602) in the Drupal handbook.
|
||||
See http://www.php.net and http://www.mysql.com for more information.
|
||||
|
||||
OPTIONAL TASKS
|
||||
--------------
|
||||
|
|
@ -47,7 +38,6 @@ OPTIONAL TASKS
|
|||
themes), the ability to log in via OpenID, fetching aggregator feeds, or
|
||||
other network-dependent services.
|
||||
|
||||
|
||||
INSTALLATION
|
||||
------------
|
||||
|
||||
|
|
@ -75,7 +65,7 @@ INSTALLATION
|
|||
|
||||
2. CREATE THE CONFIGURATION FILE AND GRANT WRITE PERMISSIONS
|
||||
|
||||
Drupal comes with a default.settings.php file in the sites/default
|
||||
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
|
||||
|
|
@ -84,18 +74,18 @@ INSTALLATION
|
|||
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 sites/default/default.settings.php sites/default/settings.php
|
||||
cp config/default/default.settings.php config/default/settings.php
|
||||
|
||||
Next, give the web server write privileges to the sites/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 sites/default/settings.php
|
||||
chmod o+w config/default/settings.php
|
||||
|
||||
So that the files directory can be created automatically, give the web server
|
||||
write privileges to the sites/default directory with the command (from the
|
||||
write privileges to the config/default directory with the command (from the
|
||||
installation directory):
|
||||
|
||||
chmod o+w sites/default
|
||||
chmod o+w config/default
|
||||
|
||||
3. CREATE THE DRUPAL DATABASE
|
||||
|
||||
|
|
@ -111,6 +101,42 @@ INSTALLATION
|
|||
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
|
||||
|
|
@ -121,27 +147,27 @@ INSTALLATION
|
|||
site settings.
|
||||
|
||||
The install script will attempt to create a files storage directory
|
||||
in the default location at sites/default/files (the location of the
|
||||
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 sites/default/files
|
||||
chmod o+w sites/default/files
|
||||
mkdir config/default/files
|
||||
chmod o+w config/default/files
|
||||
|
||||
The install script will attempt to write-protect the settings.php file and
|
||||
the sites/default directory after saving your configuration. However, you
|
||||
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 sites/default/settings.php
|
||||
chmod a-w sites/default
|
||||
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 sites/default/settings.php, it may be in another location
|
||||
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
|
||||
|
|
@ -277,12 +303,12 @@ 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 'sites'
|
||||
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 'sites/example.com/settings.php' (note that 'www.'
|
||||
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
|
||||
|
|
@ -290,26 +316,26 @@ 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:
|
||||
|
||||
sites/default/settings.php
|
||||
sites/example.com/settings.php
|
||||
sites/sub.example.com/settings.php
|
||||
sites/sub.example.com.site3/settings.php
|
||||
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:
|
||||
|
||||
sites/www.sub.example.com.site3/settings.php
|
||||
sites/sub.example.com.site3/settings.php
|
||||
sites/example.com.site3/settings.php
|
||||
sites/www.sub.example.com/settings.php
|
||||
sites/sub.example.com/settings.php
|
||||
sites/example.com/settings.php
|
||||
sites/default/settings.php
|
||||
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 sites/8080.www.example.com/. The port number will be removed according to
|
||||
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.
|
||||
|
||||
|
|
@ -320,7 +346,7 @@ 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:
|
||||
|
||||
sites/sub.example.com/:
|
||||
config/sub.example.com/:
|
||||
settings.php
|
||||
themes/custom_theme
|
||||
modules/custom_module
|
||||
|
|
|
|||
Reference in a new issue