Middlebury

WordPress Administration

Revision as of 13:34, 11 November 2011 by Adam Franco (talk | contribs)

Deploying updates

  1. Apply updates and fixes, push to the central Git repository. See WordPress Development.
  2. ssh to the production host
  3. cd to the wordpress directory
  4. run git pull

Domain Names for blogs

1. Add the ServerAlias entries to the Apache VirtualHost config at /etc/httpd/conf.d/vhost.conf. We don't need separate VirtualHosts because all of the settings are the same. We just need the main virtual host to respond under the new names:

ServerAlias middleburymagazine.com
ServerAlias www.middleburymagazine.com

Restart the webserver after making the changes.

# service httpd configtest
Syntax OK
# service httpd restart
Stopping httpd:                                            [  OK  ]
Starting httpd:                                            [  OK  ]

2. As WordPress admin, in a browser go to the network Domain settings page: Network Admin --> Settings --> Domains

Add the hostnames from step one for the blog without the Primary box checked.

3. Add the primary host-name to the allowed services list on the CAS server so that site editors can log on.

4. Set the primary host-name to have the Primary flag

If the DNS has not yet been pointed at our host and content editing is still needed before roll-out, be sure to make none of the new host-names "Primary". If none of them are primary, visitors will be redirect to http://blogs.middlebury.edu/blogname and be able to work with the blog before the DNS changes propagate. Once editing is done and you are ready for the cut-over, set the primary host-name for the blog and then make the DNS changes. Until any users' DNS caches are updated they will be redirected to the primary host-name which might send them to the old site temporarily.

5. Update the DNS.