Setup a production server using Meteor Up

This page documents the process of setting up a production server for RadGrad based upon Meteor Up.

Setup developer account

To start, you will need to create the ability for multiple developers to manage a single RadGrad installation on this server. You can do this either via multiple logins, each with sudo access, and a shared directory, or else via a single account whose password is shared amongst developers involved in production.

In this page, we will assume you (or a sysadmin) has created an admin account called "radgrad" that is used by all developers to manage this installation.

Open ports

Several ports on the server will need to be open:


Setup NetData

It is useful to have system load monitoring established for the production server. One (free) choice is NetData.

Follow their instructions to set up a monitor daemon on the production server and "claim" that server in their cloud-based dashboard service. When you are done, you can easily monitor the load on your server and even set up alerts when various thresholds are crossed. Here's a screen shot illustrating the dashboard:


In order for the mup setup command to work, you must add NOPASSWD to the sudoers file on the server as documented in SSH based authentication with sudo.

Install mup

Follow the instructions at

npm install -g mup

Setup mup.js and settings.json

In the app/.deploy directory, there are two template files: mup.sample.js and settings.sample.json.

Copy mup.sample.js to mup.js and settings.sample.js to settings.js:

cp mup.sample.js mup.js; cp settings.sample.json settings.json

Both mup.js and settings.json are ignored by git, so you can safely add credentials into those files without fear of them being committed to GitHub.

Edit these two files, adding credentials where necessary. See Philip if you need credentials.

Set up server

You can now set up the server following the directions at

mup setup

Sample invocation and output:

app/.deploy $ mup setup
Started TaskList: Setup Docker
[] - Setup Docker
[] - Setup Docker: SUCCESS
Started TaskList: Setup Meteor
[] - Setup Environment
[] - Setup Environment: SUCCESS
Started TaskList: Setup Mongo
[] - Setup Environment
[] - Setup Environment: SUCCESS
[] - Copying Mongo Config
[] - Copying Mongo Config: SUCCESS
Started TaskList: Start Mongo
[] - Start Mongo
[] - Start Mongo: SUCCESS
Started TaskList: Setup proxy
[] - Setup Environment
[] - Setup Environment: SUCCESS
[] - Pushing the Startup Script
[] - Pushing the Startup Script: SUCCESS
[] - Pushing Nginx Config Template
[] - Pushing Nginx Config Template: SUCCESS
[] - Pushing Nginx Config
[] - Pushing Nginx Config: SUCCESS
[] - Cleaning Up SSL Certificates
[] - Cleaning Up SSL Certificates: SUCCESS
[] - Configure Nginx Upstream
[] - Configure Nginx Upstream: SUCCESS
Started TaskList: Start proxy
[] - Start proxy
[] - Start proxy: SUCCESS
Next, you should run:
mup deploy

Deploy to server

Now you can deploy the current version of RadGrad in your directory to the server following the directions at

mup deploy

Sample invocation and output. This takes approximately 10 minutes on my machine to complete:

app/.deploy $ mup deploy
Building App Bundle Locally
Started TaskList: Pushing Meteor App
[] - Pushing Meteor App Bundle to the Server
[] - Pushing Meteor App Bundle to the Server: SUCCESS
[] - Prepare Bundle
[] - Prepare Bundle: SUCCESS
Started TaskList: Configuring App
[] - Pushing the Startup Script
[] - Pushing the Startup Script: SUCCESS
[] - Sending Environment Variables
[] - Sending Environment Variables: SUCCESS
Started TaskList: Start Meteor
[] - Start Meteor
[] - Start Meteor: SUCCESS
[] - Verifying Deployment
[] - Verifying Deployment: SUCCESS

After deployment finishes, the app should be live at

Setup Robo3T

A convenient way to inspect the contents of the production database is to use Robo3T.

You have the choice of downloading Studio 3T or Robo 3T. These instructions are for Robo 3T, which is simpler (and free).

After downloading and installing Robo3T, you must create a connection that includes port forwarding to the production MongoDB service.

First, create a new connection and name it appropriately:

Next, set up SSH access to the server running the MongoDB container by clicking on the 'SSH' tab. For example, here is the dialog window for defining ssh access to

If you have configured things correctly, then after pressing "Save" you'll get this window:

And after connecting, you can inspect any collection and document:

Setup APM

We use Monti APM for application monitoring.

To setup Monti APM, you will need to provide credentials in the settings.json file in the "monti" section.

Monti APM provides useful metrics for performance optimization, as well as logging client and server side run-time errors.

Here is a screenshot of one of the Monti APM screens: