Congratulations, you're this close to going live with your website on Lagoon! In order to make this as seamless as possible, we've got this final checklist for you. It leads you through the last few things you should check before taking your site live.
Routes / SSL#
Check to be sure that all routes have been set up in your
.lagoon.yml. Be aware that if you don't point the domains towards Lagoon, you should disable Let's Encrypt (LE) certificate creation, as it will lead to issues. Domains not pointing towards Lagoon will be disabled after a while in order to not exceed the Let's Encrypt quotas.
If you use Certificate Authority (CA) signed certificates, you can set
false , but leave the
insecure flag set to
Redirect. In the case of CA certificates, let your Lagoon administrator know the routes and the SSL certificate that needs to be put in place.
environments: main: routes: - nginx: - example.com: tls-acme: 'false' insecure: Allow - www.example.com: tls-acme: 'false' insecure: Allow
As soon as the DNS entries point towards your Lagoon installation, you can switch the flags:
environments: main: routes: - nginx: - example.com: tls-acme: 'true' insecure: Redirect - www.example.com: tls-acme: 'true' insecure: Redirect
As checking every page of your website might be a bit a tedious job, you can make use of mixed-content-scan. This will crawl the entire site and give you back pages that include assets from a non-HTTPS site.
If you need non-www to www redirects, make sure you have them set up in the
redirects-map.conf - see Documentation.
Check if your cron jobs have been set up for your production environment - see
To make it as smooth as possible for you to get your site pointing to our servers, we have dedicated load-balancer DNS records. Those technical DNS resource records are used for getting your site linked to the amazee.io infrastructure and serve no other purpose. If you are in doubt of the CNAME record, ask your Lagoon administrator about the exact CNAME you need to set up.
Example on amazee.io :
Before you switch over your domain to Lagoon, make sure you lower the Time-to-Live (TTL) before you go live. This will ensure that the switch from the old to the new servers will go quickly. We usually advise a TTL of 300-600 seconds prior to the DNS switch. More information about TTL.
Recommended settings for Fastly (CNAME record):#
The recommended method of pointing your domain's DNS records at Lagoon is via a CNAME record as shown below:
Alternate Settings for Fastly (A records):#
If your DNS provider does not support the use of CNAME records, you can use these A records instead. Please ensure you set up individual records for each IP listed below:
We do not suggest configuring any static IP addresses in your DNS zones. The Lagoon load balancer infrastructure may change over time which can have impact on your site availability if you configure a static IP address.
Configuring the root domain (e.g. example.com) can be a bit tricky because the DNS specification does not allow the root domain to point to a CNAME entry. Depending on your DNS provider, the record name is different:
- ALIAS at DNSimple
- ANAME at DNS Made Easy
- ANAME at easyDNS
- ALIAS at PointDNS
- CNAME at CloudFlare
- CNAME at NS1
If your DNS provider needs an IP address for the root domain, get in touch with your Lagoon administrator to give you the load balancer IP addresses.
Lagoon understands the concept of development and production environments. Development environments automatically send
nofollow headers in order to prohibit indexing by search engines.
X-Robots-Tag: noindex, nofollow
During project setup, the production environment should already be defined. If that's omitted, your environment will run in development mode. You can check if the environment is set as production environment in the Lagoon user interface. If the production environment is not set, let your Lagoon administrator know, and they will configure the system accordingly.