Go live with your Hypernode
You have copied your shop to Hypernode and tested its functionality. Now is the time to go live with your Hypernode. Follow these steps for a a smooth transition.
Table of contents
- 1 Prerequisites
- 2 Step 1: Put the site on your old host into maintenance mode
- 3 Step 2: Synchronize database and files
- 4 Step 3: Take old site out of maintenance mode (optional)
- 5 Step 4: Take hypernode out of maintenance mode
- 6 Step 5: Change your base URL to include www
- 7 Step 6: Flush Magento cache on Hypernode
- 8 Step 7: Change DNS records
- 9 Step 8: Configure cron
- 10 Step 9: Configure historical backups on Hypernode (optional)
- 11 Downgrade or cancel your previous plan
- You have verified that your site runs properly on Hypernode, including redirects, password protected areas, etc.
- You have access to the DNS settings of the domains for all your storefronts.
- You have lowered the DNS TTL for these DNS records (300 seconds is a good value).
- Check which domains will need to be configured by listing the base urls. (
- You have checked whether there are external dependencies on your shop’s IP address (for example, external suppliers who need your IP for their firewall. Bol.com is a known example).
Step 1: Put the site on your old host into maintenance mode
This will prevent data being changed while performing a last synchronization to Hypernode. Maintenance mode can easily be activated by placing a file called
maintenance.flag in the top Magento folder on your old host. (
Step 2: Synchronize database and files
Final synchronization of files and database, using the Hypernode importer on Hypernode:
hypernode-importer --host ssh.yourdomain.com --user yourdomain.com --path yourdomain.com
The importer will overwrite any local modifications made to
fpc.xml configuration files, so if you have made custom modifications (Redis config for example) between hypernode-importer runs, you should make a backup of these files.
If you have custom changes that need to be made to the site after copying to make it run on Hypernode, now is the time to apply them.
Step 3: Take old site out of maintenance mode (optional)
If you want to keep maintenance time low at the cost temporarily serving a slow site, you can change the configuration of the old site to use the new database. This step can be safely skipped.
Configuration can be taken from the new
local.xml, but this will typically just involve changing the database host to mysqlmaster.myapp.hypernode.io.
After reconfiguring the database, you can take the site out of maintenance mode by removing the maintenance flag. (
Note: from now on, database changes (orders) will be written to Hypernode, but not file changes. At this stage, do not upload new media (products) in the old Magento backend.
Step 4: Take hypernode out of maintenance mode
Remove the maintenance flag on the Hypernode, so customers accessing the new site won’t hit the maintenance page. (
Step 5: Change your base URL to include www
If you use Hypernode’s www-redirection service, ensure that the base URL of your shop starts with
www. or a subdomain such as
shop.. Otherwise, your visitors will bounce back and forth between the redirection service and the Hypernode.
Step 6: Flush Magento cache on Hypernode
Flush the cache of Magento on the Hypernode. (
Step 7: Change DNS records
NB: Using a subdomain (for example: webshop.yourdomain.com) as main URL? See our manual on configuring DNS for more information.
For all storefront URLS (not starting with WWW), the DNS records should be changed now. Remove all A records for your web domains, since the IP address of your Hypernode might change at any time. The correct configuration is for all domain names is:
www.mydomain.com CNAME myapp.hypernode.io mydomain.com ANAME or ALIAS myapp.hypernode.io
If your DNS provider doesn’t support ANAME or ALIAS records, you can use our forwarder to redirect all traffic from your naked domain.com to www.domain.com, by creating the following records:
www.mydomain.com CNAME myapp.hypernode.io mydomain.com A 188.8.131.52 mydomain.com A 184.108.40.206
See our manual on configuring DNS for more information. As the DNS changes are propagated, traffic will go to your Hypernode.
SPF records (for experts)
If you have previously configured SPF, you should also update your the SPF policy. You should include
spf.appname.hypernode.io for all domains you choose to send mail from using Hypernode.
The following example allows mail from both your mail exchangers and all your Hypernode nodes:
mydomain.com TXT v=spf1 mx:mydomain.com include:spf.appname.hypernode.io ~all
Step 8: Configure cron
Configure cron jobs to run on your Hypernode (
crontab -e), and configure them not to run on your old host (
Note that the time on Hypernode is configured to UTC, so the times used in the crontab are one or two hours later than Central European Time. More information about cronjobs can be found in Configure cronjobs on Hypernode.
Step 9: Configure historical backups on Hypernode (optional)
For Hypernode Go Big and Excellence hosting plans historical backups are available. If you need a backup, contact us via firstname.lastname@example.org. Hypernode Start and Grow do not have historic backups. If you want to have access to periodic backups, this is something you’ll have to manually configure.
Downgrade or cancel your previous plan
Have a Magento hosting plan at Byte? If you require email, domain registration and/or SSL services, you should downgrade it to one of the following plans:
- Presence: use this one if you only need domain registration and/or SSL certificates
- Personal hosting: use this one if you only need domain registration, email at Byte and NO SSL certificates
- Secure: use this one if you need domain registration, email at Byte and SSL certificates
The smartest solution would be to downgrade to a Presence plan (you have domain registration and you can order/use SSL) and then use an external mail service to provide for your email needs. Information about these plans can be found on the Presence (Dutch) and Clusterhosting (Dutch) page on www.byte.nl.