The following are instructions on how to go live from a site that has been built on a development server, and which will be using the URL of the old live website. The process involves keeping the live web-root folder the same and replacing the contents of that folder with the contents of the development folder. If your go-live follows a different process and you require assistance, contact firstname.lastname@example.org.
- Update the HTTP Root in Setup > Site Settings to point to the new domain.*
- Go to Setup > Site and click on Scan > Revert Site.
Performing a reverse scan converts all dependency tags to root relative links or absolute links, depending on the site settings.
- Perform a Find and Replace operation to update any hard-coded links from the old domain to the new one.
- Re-publish all Assets.
- Do a Dependency Scan to convert all links to DM tags again.
- Do a Site Publish.
* When you update the HTTP root for the site that is going live, if it shares the same root as your old Dev site, you will also have to update the HTTP root for your Dev site. Otherwise, both sites will publish to the same location and you run the risk of someone publishing files from the old site and overwriting files on the new site.
Most customers usually keep their old site for a while and simply update its HTTP root to point to a sub-domain (ie.: test.site.edu, or old.site.edu).
For a more comprehensive and thorough breakdown of the above steps, visit this page.
The OU Campus modules that use a site of their own, Course Catalog and sometimes Blogs, also use this process for the site to go live. Otherwise, modules are live as long as the site they are placed in is live or are linked to from a live page. For information on modules, visit the OU Campus Modules pages.