Using Drupal with comprehensive web hosting

Expand All

ssh to access.nsms.ox.ac.uk (Microsoft Windows users can download and run putty to perform this operation):

  • ssh access.nsms.ox.ac.uk
  • cd <site-name>/htdocs/
  •  

For this example we will install Drupal 7.

 

If you are not sure which version of PHP your webserver is running, you could temporarily create a php file containing:

  • <?php
  • phpinfo()
  • ?>
  •  

For full install instructions see https://www.drupal.org/documentation/install

 

  • cd <site-name>/htdocs/
  • drush dl drupal-7
  • cd drupal-<number>
  • mv * .??* ..
  • cd ..
  • rm -rf drupal-<number>
  •  

You could then edit the .htaccess file to prepend some lines to restrict access to the site until it is ready to launch, e.g.:

 

  • <IfModule mod_authz_core.c>
  • Require ip 129.67.0.0/16
  • Require ip 163.1.0.0/16
  • Require ip 192.76.8.0/26
  • </IfModule>
  • <IfModule !mod_authz_core.c>
  • Order allow,deny
  • Allow from 129.67.0.0/16
  • Allow from 163.1.0.0/16
  • Allow from 192.76.8.0/26
  • </IfModule>

Use a web browser to visit your site, then set it up:

  • Standard or minimal number of modules pre-enabled - these can be changed later
  • English
  • Enter the database name, database username and password, then click Advanced Options and enter the database host, e.g. nsmsdbXX.nsms.ox.ac.uk
  • Use a unique outgoing site email address, e.g. do-not-reply@<site-name>
  • Enter details of a maintenance account - this should have the email address of the site administrator
  • Keep in mind that by default this login page will be accessible to the whole of the internet, so passwords need to be strong
  • Create content!
  • Once the site is ready to launch, alter the .htaccess file again if needed

(See https://www.drupal.org/upgrade)

Put the site into maintenance mode and clear the caches:

  • cd <site-name>/htdocs/
  • drush vset --yes maintenance_mode 1
  • drush cc all

Back up the database:

  • mysqldump -u siteXXXX_YYYY -h nsmsdbXX.nsms.ox.ac.uk -p database-name > ../home/name-of-file.dump

Check the drupal version:

  • drush core-status --fields="Drupal version"

Back up a couple of files that the update process will overwrite:

  • cp .htaccess ../home/
  • cp robots.txt ../home/

Update drupal core (this can take a few minutes, be patient):

  • drush up drupal

Compare the two files backed up earlier, to check that nothing important has been overwritten:

  • diff .htaccess ../home/.htaccess
  • diff robots.txt ../home/robots.txt

Take the site out of maintenance mode:

  • drush vset --yes maintenance_mode 0
  • drush cc all

(Note that the "drush-backups" folder it has created is not within the web site files or quota, it is in the user's home directory on access.nsms.ox.ac.uk, which is not backed up or accessible to other users)

Check that the site works, then update individual modules one at a time.

If a plugin or other code cannot be updated or is no longer supported, then consider whether it is safe to use.

 

 

 

 

 

 

 

 

 

 

 

 

Get support


Local IT support provide your first line of on-the-spot help

FIND MY LOCAL IT TEAM

 

Common requests and fault reports can be logged using self-service

   USE IT SELF-SERVICE    

   LOG A SUPPORT CALL    

VIEW MY SUPPORT CALLS  

The central Service Desk is available 24x7 on +44 1865 6 12345

 

If you do not have an SSO account you can use this form to contact the Service Desk