Moving/Migrating S3MediaVault from Test/Staging Domain to Main Domain
If you are planning to setupS3MediaVault on a test or staging domain, then here are some things to consider:
- A sub-domain is technically a different domain compared to your main domain. So subdomain.example.com and example.com are actually completely different domains, though they are on the same domain.
- If you test S3MediaVault on a sub-domain, it won't automatically work on the other even if you move over all of the files and database tables.
- However, a WordPress installation in a sub-folder would still be the same domain as the main one, even if it's a new WordPress installation. So a new WordPress installation at example.com/staging/ and the WordPress installation at example.com would both be technically the same domain.
- So if you're planning on testing S3MediaVault somewhere other than your main website, then it's best to install WordPress in a sub-folder (like /staging or /test) and then setup, configure and test S3MediaVault there. Then, when you move everything over to the main WordPress installation, it will work seamlessly without having to re-do any of the setup or configuration.
- S3MediaVault ties your S3 bucket and CloudFront distribution to your domain for security purposes. So if you test S3MediaVault on a different domain and then switch the license back to the main domain, then even though it's the same bucket, none of your Streaming Videos will work. Standard videos will work, as long as you do the step below.
- Every time you move S3MediaVault to a different domain (or even if you move away and move back), you have to click on "Save Settings" on the new site, create a new CloudFront distribution, and re-prepare all streaming videos, which could be expensive depending on how many videos you have. This is if you're going to be using CloudFront. If not, then everything will work fine as long as you save the settings again, thus tying the bucket name again to the new domain.
- Preparing videos for streaming is only required if you are going to create "Streaming Videos" which are different from "Standard Videos".
- Ideally, you should just test it on the final website where it will continue to exist, that way, you don't have to re-prepare all of the videos (this applies only if you're creating "Streaming Videos" that are really hard to download).
Moving/Migrating S3MediaVault from One Domain To Another
Make sure you move the <wpprefix>_s3mv_ database tables when you move S3MediaVault. If you have not worked with MySQL database tables before, we recommend that you don't start with this, because if you mess up the tables, you could lose all or most of your S3MediaVault settings. We can help you with migrating your entire S3MediaVault installation for a fee. Please open a ticket at https://DigitalAccessPass.com/support/
If you have set up "Streaming" videos/audio:
S3MediaVault ties your S3 bucket and CloudFront distribution to your domain for security purposes. So your Streaming Videos/audio will not work.
- Copy over the S3 (and CloudFront, if using it) private and public keys from your previous website's settings. Click "Save".
- Copy over the previous S3 bucket name,
- Click on "Create new CloudFront distribution" which will create a new CloudFront distribution, because your old CloudFront distribution is tied to your old domain and you will be able to use that any more.
- Go to the S3MediaVault Media page. Click on "Prepare for Streaming" on any one video (just one for now). Wait for about 5-10 minutes (only the first time).
- Go to the page that has a shortcode with that video, and test to make sure the streaming video is working.
- If it's working, then now click on "Prepare All Video & Audio for Streaming" (there is a button for doing that on the Media page under the section "Bulk Prepare Files For Streaming").
- Test all shortcodes and make sure they're working. That's it.
If you have set up "Standard" video/audio:
- Copy over the S3 (and CloudFront, if using it) private and public keys from your previous website's settings. Click "Save".
- Copy over the previous S3 bucket name,
- If using CloudFront, click on "Create new CloudFront distribution" which will create a new CloudFront distribution, because your old CloudFront distribution is tied to your old domain and you will be able to use that any more. If not using CloudFront, ignore this step.
- Test all shortcodes and make sure they're working. That's it.