VIP Go platform specific
This document is for sites running on VIP Go.
When you wish to retire a site from VIP Go, we ask that you notify the VIP team via a support ticket 30 days in advance of the site retirement date. At the end of this period, we will normally retire the site(s) along with the non-production environment(s) and update your account’s billing details as per our agreement.
In the case of selective retirement of subsites within a Multisite, we will delete/archive the requested sites and production monitoring for these subsites sites will be disabled.
In order to archive or migrate the site to other hosting, you will need several elements, and we cover these below.
Codebase / GitHub repository #
You may wish to first read about the structure of your VIP Go codebase.
If the GitHub repository will no longer be used by an active VIP Go site, once the site(s) have been retired, the associated GitHub repository will be removed as well so please ensure you have a local copy of the repository saved. You can either download a copy of the code in your VIP Go repository as it is, clone a copy of the Git repository, to retain the version history and all changes, or we can transfer the repository to your GitHub account, to retain all version history, GitHub issues, GitHub pages, etc.
Download a copy of your codebase #
- Navigate to your VIP Go repository on GitHub
- Select “Clone or Download” from the front page of your repository
- Select “Download ZIP”
- Check the contents, and save the file
Clone your repository #
GitHub maintains documentation on cloning a GitHub repository.
Transfer a repository #
If you would like to transfer your VIP Go repository to your GitHub account, please contact us; read more about repository transfers.
Files and data #
If you would like an archive of all files that have been uploaded to your site, please contact us. The archive will be supplied with the same directory structure as the file uploads. The data will be supplied as SQL from the