External Rehosting

An external rehosting involves moving an external website (non-USD website) from some other company or institution's servers onto USD's servers. Rehosted websites appear identically to the user before and after the rehosting.

Rehostings are handled exclusively by allowing access to the vendor (the outside company or institution that created the site). The vendor then does all of the work of relocating and mainting the website going forward.

The web team only provides access for the vendor to modify files on USD's servers using the process and steps below. No other support is available.

Setup for web professional access: upload web-based content and programming

  1. Contact the ITS Help Desk to begin the process of creating a USDOne account.
    1. NOTE: this account must be a full USDone account, not a VPN only account.
    2. In order to view the website on our development server, the consultant will need a VPN account. 
  2. Once the account has been provisioned and claimed request your consultant to go to https://github.sandiego.edu. They will need to log into the system using their USDOne credentials. 
  3. Open a web-request and provide your requirements for disk space and whether a database will be needed.
    1. Upon receipt of the web request, our Senior Web Administrator will establish a code repository using GITHUB enterprise and tie the repository to our Continuous integration/deployment system, with the following abilities:
      1. to publish to our development environment (http://build.sandiego.edu/) using the repository branch build
      2. to publish to our staging site (http://staging.sandiego.edu/) using the repository branch staging
    2. Upon acceptance of the new code,  the Senior Web Administrator will establish the final production connection. Your consultant will be able to publish to the production site at the URL designated by using the repository branch Release.
    3. Please note: depending on the complexity of the pages/site your consultant is building, we may require Unit testing, and code review to release the code on our production servers.

Uploading Files and General File Management

  • Once the two accounts noted above are granted you will be able to commit to the GitHub repo and your files will automatically publish to the provisionned area.
  • The repository your conslutant will be working with will be a mirror of what is available in the production system. So, if they need to 'archive' a page (such as from a dean's report), they will be able to add directories to the repo and move existing files into that folder.

Before

After