Going Live#
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.
Check your .lagoon.yml
#
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 tls-acme
to false
, but leave the insecure
flag set to Allow
or Redirect
. In the case of CA certificates, contact amazee.io support with 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: tls-acme
to true
and insecure
to Redirect
environments:
main:
routes:
- nginx:
- example.com:
tls-acme: 'true'
insecure: Redirect
- www.example.com:
tls-acme: 'true'
insecure: Redirect
Note
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.
Redirects#
If you need non-www to www redirects, make sure you have them set up in the redirects-map.conf
- see Documentation.
Cron jobs#
Check if your cron jobs have been set up for your production environment - see .lagoon.yml
.
DNS#
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, contact amazee.io support about the exact CNAME you need to set up.
Example on amazee.io : <region-identifier>.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.
Info
This information only relates to amazee.io hosted projects, and will shortly be removed from these docs and added to amazee.io specific ones
Recommended settings for Fastly:#
Subdomains (CNAME)#
The recommended method of pointing your subdomain's (e.g. www.example.com) DNS records at Lagoon is via a CNAME record as shown below:
CNAME
: cdn.amazee.io
Root domains (A/AAAA)#
Configuring the root domain (e.g. example.com.) can be tricky because the DNS specification does not allow root domains to point to a CNAME. Therefore, the following A and AAAA records should be used. Please ensure you set up individual records for each IP listed below:
A
:151.101.2.191
A
:151.101.66.191
A
:151.101.130.191
-
A
:151.101.194.191
-
AAAA
:2a04:4e42::703
AAAA
:2a04:4e42:200::703
AAAA
:2a04:4e42:400::703
AAAA
:2a04:4e42:600::703
Production environment#
Lagoon understands the concept of development and production environments. Development environments automatically send noindex
and 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 amazee.io support know, and they will configure the system accordingly.