Library & ITS Wiki
Difference between revisions of "WordPress Administration"
Adam Franco (talk | contribs) (Added tag: 'Web Application Development') |
Adam Franco (talk | contribs) |
||
| Line 1: | Line 1: | ||
= Deploying updates = | = Deploying updates = | ||
| + | # Apply updates and fixes, push to the central Git repository. See [[WordPress Development]]. | ||
| + | # ssh to the production host | ||
| + | # cd to the wordpress directory | ||
| + | # run <code>git pull</code> | ||
= Domain Names for blogs = | = Domain Names for blogs = | ||
| + | 1. Add the ServerAlias entries to the Apache VirtualHost config at <code>/etc/httpd/conf.d/vhost.conf</code>. 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: | ||
| − | [[ | + | <pre>ServerAlias middleburymagazine.com |
| − | + | ServerAlias www.middleburymagazine.com</pre> | |
| + | |||
| + | Restart the webserver after making the changes. | ||
| + | |||
| + | <pre># service httpd configtest | ||
| + | Syntax OK | ||
| + | # service httpd restart | ||
| + | Stopping httpd: [ OK ] | ||
| + | Starting httpd: [ OK ]</pre> | ||
| + | |||
| + | 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. | ||
| + | |||
| + | {{Note|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. }} | ||
| + | |||
| + | 3. Set the primary host-name to have the "primary" flag and update the DNS. | ||
Revision as of 11:53, 11 November 2011
Deploying updates
- Apply updates and fixes, push to the central Git repository. See WordPress Development.
- ssh to the production host
- cd to the wordpress directory
- 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.
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.
3. Set the primary host-name to have the "primary" flag and update the DNS.
