Hi guys - it looks like the bottom "Edit this page on GitHub" links on each page are broken (the top "Edit on GitHub" links are working). I took a quick look at the source, and it looks like you'll just need to update to the latest hexo-theme-meteor version. This appears to now be fixed in the page.ejs template. Thanks!

Documentation here seems outdated. IT not only references as to docker registry images updated 2 and 4 years ago, Ubuntu 14.04 (support of which ended almost exactly 1 year ago) but also mentions node v8.9.3

Dead link on this page Troubleshooting > 503

https://github.com/meteor/galaxy-docs/blob/master/content/deploy-troubleshooting.md

Like in Docs:

All Galaxy customers can submit support cases from within Galaxy and receive Basic online support for deployment-related questions. There is no guaranteed response SLA for Basic support but questions are typically answered within 1-2 business days.

How to contact support is not specified. :/
At least explain how to 'submit support cases'.

Thanks.

When following the instructions for redirecting the root domain to the www subdomain in the Galaxy docs, I couldn't get it to work with HTTPS.

After some digging into the AWS docs, it seems like redirecting HTTPS is not possible with this simple setup described in the Galaxy docs.

The sites must use HTTP, because the redirect can't connect to Amazon S3 over HTTPS.
https://aws.amazon.com/premiumsupport/knowledge-center/redirect-domain-route-53/

The solution for me was to add a CloudFront distribution (and a new cert) and point the A record of the root domain to that (instead of pointing it to the S3 bucket).

Amazon S3 website endpoints do not support HTTPS or access points. If you want to use HTTPS, you can use Amazon CloudFront to serve a static website hosted on Amazon S3.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteEndpoints.html

Did I miss anything here? The AWS docs seem to contradict the Galaxy docs.

On this page -> https://github.com/meteor/galaxy-docs/blob/master/content/environment-variables.md

It says this:

The following is an example setting for the MAIL_URL environment variable: smtp://postmaster%40your.mailserver.address.com:[email protected]:587

settings.json example

{
  "galaxy.meteor.com": {
    "env": {
      "MONGO_URL": "...",
      "MONGO_OPLOG_URL": "..."
    }
  },
  ... other keys can go here
}

but there is no example. Plus, I think ... other keys can go here might be missing some braces.

the reference link here https://galaxy-guide.meteor.com/apm-make-your-app-faster.html is broken it goes to this page https://kadira.io/academy/meteor-performance-101

From https://galaxy-guide.meteor.com/encryption.html#lets-encrypt:

Let's Encrypt certificates are not available for wildcard (*.) domains.

Looks like Let's Encrypt added this ability earlier this year: https://community.letsencrypt.org/t/acme-v2-production-environment-wildcards/55578

Is it possible with Galaxy?

Docs: https://github.com/meteor/galaxy-docs/blob/2200417b9f1be8028444c662568fbccc3d77d086/source/apm-make-your-app-faster.md#do-server-side-aggregations

Please see meteor/meteor#9993 (comment) for more info.