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,22 +13,22 @@ Prior to upgrading, you should ensure that:
|
|||
|
||||
Let's begin!
|
||||
|
||||
1. Back up your Drupal database and site root directory. Be especially sure
|
||||
to back up your "sites" directory which contains your configuration file,
|
||||
added modules and themes, and your site's uploaded files. If other files
|
||||
1. Back up your Drupal database and site root directory. Be especially sure
|
||||
to back up your "config" directory which contains your configuration file,
|
||||
added modules and themes, and your site's uploaded files. If other files
|
||||
have modifications, such as .htaccess or robots.txt, back those up as well.
|
||||
|
||||
Note: for a single site setup, the configuration file is the "settings.php"
|
||||
file located at sites/default/settings.php. The default.settings.php file
|
||||
file located at config/default/settings.php. The default.settings.php file
|
||||
contains a clean copy for restoration purposes, if required.
|
||||
|
||||
For multisite configurations, the configuration file is located in a
|
||||
structure like the following:
|
||||
|
||||
sites/default/settings.php
|
||||
sites/example.com/settings.php
|
||||
sites/sub.example.com/settings.php
|
||||
sites/sub.example.com.path/settings.php
|
||||
config/default/settings.php
|
||||
config/example.com/settings.php
|
||||
config/sub.example.com/settings.php
|
||||
config/sub.example.com.path/settings.php
|
||||
|
||||
More information on multisite configuration is located in INSTALL.txt.
|
||||
|
||||
|
@ -52,7 +52,7 @@ Let's begin!
|
|||
|
||||
7. Unpack the new files and directories into the Drupal installation directory.
|
||||
|
||||
8. Copy your backed up "files" and "sites" directories to the Drupal
|
||||
8. Copy your backed up "files" and "config" directories to the Drupal
|
||||
installation directory. If other system files such as .htaccess or
|
||||
robots.txt were customized, re-create the modifications in the new
|
||||
versions of the files using the backups taken in step #1.
|
||||
|
|
Reference in a new issue