Middlebury

Difference between revisions of "WordPress Administration"

m (Domain Names for blogs: Add step to add domain to CAS services directory.)
 
(6 intermediate revisions by 2 users not shown)
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 =
+
#Apply updates and fixes, push to the central Git repository. See [[WordPress Development]].
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:
+
#ssh to the production host
 +
#cd to the wordpress directory
 +
#run <code>git pull</code>
  
<pre>ServerAlias middleburymagazine.com
+
= Domain Names for blogs  =
ServerAlias www.middleburymagazine.com</pre>
 
  
Restart the webserver after making the changes.
+
1. Ask the client (if he/she owns and manages his/her own domain) or CSNS (if it's a middlebury.edu subdomain) to have the address point to the IP address for orator (140.233.2.239).
  
<pre># service httpd configtest
+
2. Enter the Domain Mapping settings page in the WordPress admin interface.
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*
+
3. Enter the site ID of the WordPress site and the domain information, and click Save.
  
Add the hostnames from step one for the blog.
+
4. Add the domain to the CAS services directory.
  
{{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. }}
+
{{Note|If the DNS has not yet been pointed at our host and content editing is still needed before roll-out, be sure the "Primary" checkbox is not checked. If none of them are primary, visitors will be redirected to http://sites.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, edit the entry on the Domain Mapping settings page and set the appropriate domain to "Primary". 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.
 
  
 
[[Category:WordPress]]
 
[[Category:WordPress]]
 +
[[Category:Web Application Development]]

Latest revision as of 11:53, 14 June 2016

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. Ask the client (if he/she owns and manages his/her own domain) or CSNS (if it's a middlebury.edu subdomain) to have the address point to the IP address for orator (140.233.2.239).

2. Enter the Domain Mapping settings page in the WordPress admin interface.

3. Enter the site ID of the WordPress site and the domain information, and click Save.

4. Add the domain to the CAS services directory.

If the DNS has not yet been pointed at our host and content editing is still needed before roll-out, be sure the "Primary" checkbox is not checked. If none of them are primary, visitors will be redirected to http://sites.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, edit the entry on the Domain Mapping settings page and set the appropriate domain to "Primary". 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.
Powered by MediaWiki