User:Aeric/Old Steps for a New Release

From AgileApps Support Wiki
< User:Aeric
Revision as of 00:54, 13 October 2012 by imported>Aeric (Created page with "====Setup: On Local System==== # In <tt>/lj__{retired_version}__/LocalSettings.php</tt>: #:* <tt>$wgScriptPath = "/lj__{retired_version}__"</tt> #:* <tt>$wgArticlePath = "/lj__{r...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Setup: On Local System

  1. In /lj__{retired_version}__/LocalSettings.php:
    • $wgScriptPath = "/lj__{retired_version}__"
    • $wgArticlePath = "/lj__{retired_version}__/$1"
    • Comment out Google analytics in LJ skin. (Leave its variables alone.)
  2. Rename robots.txt_ALLOW to robots.txt to disable robots.
  1. In /lj__{now_curent_version}__/LocalSettings.php:
    • $wgScriptPath = "/wiki"
    • $wgArticlePath = "/wiki/$1"
    • Uncomment Google analytics in LJ skin. (Leave its variables alone.)
  2. Rename robots.txt to robots.txt_ALLOW to enable search robots.

Setup: On the Server

  1. Start VPN
  2. Login as root using PuTTY or SSHshell
  3. Edit /etc/httpd/conf.d/mediawiki.conf
    Alias /wiki /user/share/mediawiki/lj__(now_current_version)
    (For sanity's sake, move that line and accompanying comment so it is in front of the appropriate <Directory> section.)

Deploy

Do these steps as close to simultaneously as possible:

  1. In FileZilla, lj{old_version}/
    • Upload LocalSettings.php
    • Rename robots.txt_ALLOW to robots.txt to disable robots.
  2. In FileZilla, lj(new_version)
    • Upload LocalSettings.php
    • Rename robots.txt to robots.txt_ALLOW to enable search robots.

Then in the SSH shell, do an Apache cold start:

  1. service httpd stop
    (The service has to be down for cache clearing to work properly).
  2. htcacheclean -r -p/var/cache/mod_proxy
    Learn more: http://httpd.apache.org/docs/2.2/programs/htcacheclean.html
  3. service httpd start, and ignore error
    "Could not reliably determine the server's fully qualified domain name"

Notepad.png

Note: The cold start takes negligible time, and unlike a reload or restart, there is no process optimization, therefore no shortcuts--which makes "correct result" the most probable outcome.