codesignal/meteor-cloud repository overview

⁠Intro

This Dockerfile is used as a stable image for Meteor Cloud deployments.

Learn more here:

• https://cloud-guide.meteor.com/base-image-packages.html⁠
• https://cloud-guide.meteor.com/custom-base-images.html⁠
• https://github.com/meteor/galaxy-images⁠

⁠Build Image

Run docker build -t <public_docker_repo>:<tag> . in this directory.

⁠Push image

Run docker push <public_docker_repo>:<tag>

⁠Use image in Meteor Cloud

In order for Meteor Cloud to know to use the custom image you've built, see https://cloud-guide.meteor.com/custom-base-images.html⁠. In particular, you will need to modify the settings.json used during the deploy to point to the image.

To have the deploy work as expected, the settings JSON needs to be set up according to: https://cloud-guide.meteor.com/custom-base-images.html⁠

In particular, the following fields should be set:

{
  "galaxy.meteor.com": {
    "env": { "DD_API_KEY": "datadog_api_key_string", "DD_ENV": "<environment>", DD_EXTRA_TAGS": "" },
    "baseImage": {
      "repository": "public_docker_repo_of_built_custom_image",
      "tag": "tag_of_the_image_to_use"
    }
  }
}

⁠Datadog Tags

The Meteor Galaxy environment provides certain environment variables as described here: https://galaxy-guide.meteor.com/container-environment.html#env-vars⁠. Please see app/run.sh to see the ones currently collected. Any additional Meteor Galaxy environment variables should be added there as well.

Other tags can be specified in the settings.json by modifying DD_EXTRA_TAGS. DD_EXTRA_TAGS should be a comma-separated list of quote-escaped strings. For example, DD_EXTRA_TAGS could be "\"machine_type:meteor_app\", \"foo:bar\"".