mup

Meteor Up

Production Quality Meteor Deployments

Meteor Up is a command line tool that allows you to deploy any Meteor app to your own server.

You can install and use Meteor Up on Linux, Mac and Windows. It can deploy to servers running Ubuntu 14 or newer.

This version of Meteor Up is powered by Docker, making deployment easy to manage and reducing server specific errors.

Read the getting started tutorial.

Features

• Single command server setup
• Single command deployment
• Deploy to multiple servers, with optional load balancing and sticky sessions
• Environment Variable management
• Support for settings.json
• Password or Private Key (pem) based server authentication
• Access logs from the terminal (supports log tailing)
• Support for custom docker images
• Support for Let's Encrypt and custom SSL certificates

Roadmap

Server Configuration

• Auto-restart if the app crashes
• Auto-start after server reboot
• Runs with docker for better security and isolation
• Reverts to the previous version if the deployment failed

Installation

Meteor Up requires Node v8 or newer. It runs on Windows, Mac, and Linux.

npm install -g mup

mup should be installed on the computer you are deploying from.

Using Mup

• Getting Started
• Docs

Meteor compatibility

Mup supports Meteor 1.2 and newer. To use Meteor 1.4 and newer, you will need to change the docker image. A list of docker images is available here.

Support

First, look at the troubleshooting and common problems sections of the docs. You can also search the github issues.

If that doesn't solve the problem, you can:

• Create a Github issue
• Chat on Gitter

Contributors

This project exists thanks to all the people who contribute. [Contribute].

Backers

Thank you to all our backers! 🙏 [Become a backer]

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

Changelog

1.5.4 - September 19, 2021

• Increase worker_connections in nginx (@markdowney)
• When setting config.privateDockerRegistry, the host option is now optional and defaults to the docker hub registry
• Moved Prepare Bundle and Push Bundle to separate tasks. This will allow creating hooks that run between those two steps
• Before building the app, it now deletes the previous build. This should fix the very rare situations where mup deployed the previous build. This can be disabled by setting the app.buildOptions.cleanBuildLocation option to false
• Fix mup status when the config does not have a servers object
• Reduced unnecessary output in the deploy check script
• Mup now sets config.app.buildOptions.buildLocation to the default value while preparing the mup config, making the build location available to other plugins and hooks. You can also see the build location by running mup validate --show
• Fix mup meteor status when mup uses a non-root user on the server

Prepare Bundle Locally

Mup can build the docker image locally instead of on the remote server, which can be faster and avoids taking resources away from anything else running on the servers. This version has some fixes and performance improvements:

• When preparing the bundle locally, mup will try to use the docker registry api to change image tags instead of the much slower method of pulling and pushing the images
• Fix getting node version when app.docker.prepareBundleLocally is enabled (@Floriferous)
• Fix creating dockerignore file while building bundle locally. This should make building the docker image much faster

Plugin API

• prepareConfig is now passed an instance of the plugin api as the second argument