On this page:
Follow the steps outlined below to migrate your IU Web Framework site from Webserve to the Sitehost service.
The following is not intended for IU Web Framework sites that have been customized, integrated with applications outside the WCMS, protected with custom .htaccess
files, or had scheduled tasks (cron jobs) set up. To determine if your site has been customized and to migrate a site with customizations, see ARCHIVED: Migrate your customized IU Web Framework site to Sitehost.
If your site doesn't use the IU Web Framework, follow the ARCHIVED: Sitehost migration guide instead.
Verify that Two-Step Login (Duo) is enabled for the group account for which you want to request Sitehost; see Use Two-Step Login (Duo) with a group account.
If prompted, log in with your IU username and passphrase.
A code chunk is used by an IU Web Framework site to output code such as PHP, JavaScript, or HTML.
If any of your site's code chunks contain hard-coded paths to other files on Webserve, you'll need to update these code chunks to reflect the new file paths used by Sitehost. Replace <account>
with your group account name when performing the steps below:
/ip/<account>/www
and /ip/<account>/wwws
with /groups/<account>/web
/ip/<account>/
with /groups/<account>/
www
and wwws
with web
If you have a MachForm installation on your Webserve account, see MachForm migration instructions on GitHub.
In the _php
folder, edit the .htaccess
file and delete the Satisfy Any
and Allow from all
directives, as they are not used in Apache 2.4.
Each of your site's Transports must be updated using the WCMS Manager Tools to reflect new Transport names, host names, and server directories.
For the Transport labeled "TEST":
Sitehost – Test
.ssh.sitehost-test.iu.edu
./groups/<account>/
.For the Transport labeled "LIVE" or "PRODUCTION":
Sitehost – Production
.ssh.sitehost.iu.edu
./groups/<account>/
.Each of your site's Destinations must be updated in the WCMS to reflect the new directory paths in Sitehost. You should update current Destinations. Creating new Destinations will require updating Content Types. Update each Content Type by adding any new Destinations to the Content Type's Publishable Options.
For the Destination labeled "TEST":
web
.Sitehost - Test
.For the Destination labeled "LIVE" or "PRODUCTION":
web
.Sitehost - Production
.You'll need to update the staging URL in your site's Settings block in the WCMS. The Settings block is located toward the bottom of your site's root folder.
<account>.sitehost-test.iu.edu
.The IU Web Framework setup script prepares your Sitehost-test and Sitehost account to serve your IU Web Framework website. Follow the directions below to run the setup script.
For your test Sitehost account:
<username>
with your personal IU username (not the group account name): ssh <username>@ssh.sitehost-test.iu.edu
.<account>
with the group account name: become <account>
.cd
into the web directory./groups/iuframe/bin/setup_framework
.<account>.sitehost-test.iu.edu
.ls -a
.gwassets/
.htaccess
.user.ini
robots.txt
For your production Sitehost account, follow the steps above, replacing instances of sitehost-test
in URLs with sitehost
. In step 9, replace the URL <account>.sitehost-test.iu.edu
with your virtual URL (for example, iuframe.iu.edu
). If your site does not have a virtual host, enter the following URL, replacing <account>
with the group account name: <account>.sitehost.iu.edu
.
Publish your site to Sitehost's test server to confirm your site is working as expected before publishing to Sitehost's public-facing production server.
<account>.sitehost-test.iu.edu
to verify your site is working as expected. Contact Web Services Support if you're unable to get your site to work on Sitehost's test server.To publish your site to Sitehost's production server, follow the steps below:
Testing your site on the Sitehost production server requires adding your virtual host to Sitehost without requesting a DNS change. If you are not using a virtual host, then you can view your site on Sitehost by going to <account>.sitehost.iu.edu
.
If prompted, log in with your IU username and passphrase.
You will receive a confirmation email when your virtual host request is approved. Allow up to 30 minutes from receiving the confirmation email for the virtual host to be installed on Sitehost.
https://<website_url>/sitehostmigrationtest
, replacing <website_url>
with your site's virtual host URL (for example, iuframe.iu.edu
).You will now see your site as rendered by the Sitehost servers. The site title will begin with "Testing - ". Repeat the two steps listed above if clicking the link on the intermediate page does not take you to your site as rendered by the Sitehost servers.
When you have finished the above steps:
Also, you may contact Tier 2 to send the account names and site URLs that you migrated.
Site migrations require a DNS change, which will take effect by 8am on the following business day after you receive confirmation of the request.
When the DNS changes take effect, Webserve administrators will lock your Webserve account. If you need your account unlocked, contact Tier 2.