Drupal 5.x
Drupal and Virtual Host Proxies on the WWW Servers
Posted April 13th, 2012 by John BickarIn fall 2011, the web infrastructure team in IT Services made some changes to how virtual host (vhost) proxies are handled. Previously, all proxies were on a dedicated pool of proxy servers (proxy1.stanford.edu, proxy2.stanford.edu, proxy3.stanford.edu). This configuration required the use of the Reverse Proxy module. The infrastructure team is in the process of moving all existing proxies onto the www servers themselves.
Boost
Posted December 8th, 2011 by John BickarOverview
Boost "provides static page caching for Drupal enabling a very significant performance and scalability boost for sites that receive mostly anonymous traffic". With the move of proxies to the WWW servers (January 2012), it is possible to install and configure it in the Stanford Leland web environment.
Create a Development Drupal Environment
Posted December 8th, 2011 by John BickarThese instructions describe how to set up a development copy of your live Drupal site within the Stanford web environment.
Benchmarking Site Performance with ApacheBench
Posted November 3rd, 2011 by John BickarApacheBench (ab) is "a tool for benchmarking your Apache Hypertext Transfer Protocol (HTTP) server." It is built in to most current versions of Mac OS X and Linux. It's a quick way of sending multiple requests to a website and timing how long they take.
Basic Test
At its most basic, ab can perform successive and/or concurrent load tests on a webpage. Run the following command in the Terminal (Mac OS X; if you don't have OS X, ab is installed on the corn cluster machines):
Drush PHP Error
Posted July 26th, 2011 by John BickarNote that this error only occurs on Leland servers, since the retirement of pubsw.
If you get an error like this when running any drush command:
php: error while loading shared libraries: libmysqlclient.so.15: cannot open shared object file: No such file or directory
Take a look at your ~/.cshrc file. In it, you will see a few lines like the following:
Force Proxied Sites to Load via the Vanity URL
Posted November 12th, 2010 by John BickarIf you have a website at https://ponies.stanford.edu that is pointing to a Drupal install at https://www.stanford.edu/group/ponies/cgi-bin/drupal, and you want to force loading through the Vanity URL only (and avoid the broken CSS and links kerfuffle), you will need to modify the .htaccess file at the root of your drupal install, and add the following code right after the line that starts with RewriteBase.
Reverse Proxy
Posted October 22nd, 2010 by John BickarSummary
This module provides URL rewrites for integrating Drupal with a Reverse Proxy service. It was developed by the Stanford University Open Source Lab for integrating with the Virtual Host Proxy Service provided by Stanford University ITS (aka, "Vanity URL").
Private vs. Public method in file system option
Posted January 15th, 2010 by izaksWhen public method (default) is used in file system, you cannot upload files and do not see images via WYSIWYG editor (e.g. TinyMCE) with IMCE module to upload images
Fix: (per email from mrmarco )
In the .htaccess file within your file upload directory (e.g., sites/default/files/.htaccess, sites/files/.htaccess or files/.htaccess),
comment out the lines:
Drush
Posted November 12th, 2009 by John BickarWhat Is Drush?
Drush (a portmanteau of Drupal Shell) is a Linux application that allows you to perform many common tasks (such as installing and updating modules, clearing caches, viewing and deleting watchdog messages, etc.) from the command line. It's a handy tool, especially if you maintain a lot of Drupal sites.
