Properly configuring caching on a Drupal site is one of the most important things that a site administrator can do to improve performance. Caching represents a tradeoff between speed and "freshness" of content, however. There are some tools, such as the Boost crawler, that can prime your cache.
(See also: Load Page Cache after Cron Runs.)
If you want to use drush to download from Stanford's Drupal Features server, use the following syntax:
drush dl projectname --source=http://drupalfeatures.stanford.edu/fserver/projectname/core.version
E.g., to download webauth for Drupal 7, use:
This quick note outlines the additional steps required for installing Drupal 8 on the central web infrastructure (www.stanford.edu and AFS). In other words, it doesn't show all the steps (download Drupal, untar it, etc.), just the few steps needed that are special to our infrastructure.
Rationale for This Document
An upgrade of a Drupal 6 website is a complex proposition. As a general rule of thumb, many professional Drupal development teams approach a major Drupal version upgrade as a new site development project, and estimate anywhere from 60-80% of the original development resources (time, money) for the upgrade.
Ever get frustrated about the output from
'--extra="-t"' to your
'drush sqlq' command, and get a nicely-formatted table. (
"--extra" allows you to include any options you would pass to
'man mysql' to see more options to pass to
Developers working with sites on www.stanford.edu don’t get direct access to Apache’s error log. To troubleshoot your PHP applications, you can create a local php.ini file with the lines below. This will redirect PHP errors to a file of your choosing. Make sure to remove these lines and the file containing the errors once you are done troubleshooting to avoid disclosing the internal workings of your application.
There are two ways you can run Drupal 6.x at Stanford.
Request your Drupal 6.x site on the Stanford Sites service. This is open to everyone, including individuals. Installation is easy and code updates and maintenance are handled by IT Services. You can't install your own modules or themes, but installations come with plenty of pre-installed modules chosen by the community. Read more at sites.stanford.edu.
AFS gets backed up nightly, and most AFS spaces (group, dept, and user) have a hidden directory, named .backup, that provides instantaneous access to the previous night's backup.
Here's what to do if that .backup directory does not appear.
SSH into one of the timeshares (e.g., corn), cd to the root directory of the dept/group/user, and run the following command:
fs mkmount -dir .backup -vol <name-of-volume>.backup
If you get the befuddling message:
Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded
you can just run:
Or, if that doesn't work:
git pull origin master
The above might seem obvious to some, but Googling "git fast forward" proved surprisingly unfruitful. HTH.