Recently I had to start hosting a Meteor app on Ubuntu. The process is pretty straightforward however there are a few gotchas. This post is really just to help me remember in the future.
First, clone your repo on the target server or move the source files there before you compile/build the app. This is important if you are using a different OS than what your server is. I ran into issue when compiling it on OSX and moving it to Ubuntu.
After moving the files, install meteor.
|
1 |
curl https://install.meteor.com/ | sh |
Then compile your app
|
1 |
meteor build . |
It will create a archive for you.
Extract it to the directory you will host the app
|
1 |
tar -zxf myapp.tar.gz |
cd into the server folder
|
1 |
cd /var/www/myapp/bundle/programs/server |
install node modules
|
1 |
npm install |
install pm2
|
1 |
npm install -g pm2 |
cd back to the app bundle dir
|
1 |
cd /var/www/myapp/bundle |
create a process.json file
|
1 |
nano process.json |
add your configuration
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
{ "apps": [ { "name": "myapp", "script": "./bundle/main.js", "log_date_format": "YYYY-MM-DD", "exec_mode": "fork_mode", "env": { "PORT": 3000, "MONGO_URL": "mongodb://127.0.0.1/myapp", "ROOT_URL": "https://myapp.example.com/", "BIND_IP": "127.0.0.1" } } ] } |
create a shell script
|
1 |
nano run.sh |
add bash script
|
1 2 3 4 5 |
#!/bin/sh # starts pm2 and watches the process pm2 start process.json -i max --watch |
make it executable
|
1 |
chmod +x run.sh |
run the bash script
|
1 |
./run.sh |
run pm2 startup
|
1 |
pm2 startup |
this will output a command to run, run it
save current process
|
1 |
pm2 save |
All set! Check the status of your app
|
1 |
pm2 list |
You should see something similar to this
Also, here is a sample nginx site configuration using Let’s Encrypt SSL
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 |
server_tokens off; # for security-by-obscurity: stop displaying nginx version # this section is needed to proxy web-socket connections map $http_upgrade $connection_upgrade { default upgrade; '' close; } server { listen 443 ssl; root /var/www/myapp/bundle/; #index index.html index.htm; server_name myapp.example.com; ssl_certificate /etc/letsencrypt/live/myapp.example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/myapp.example.com/privkey.pem; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_prefer_server_ciphers on; ssl_dhparam /etc/ssl/certs/dhparam.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SH$ ssl_session_timeout 1d; ssl_session_cache shared:SSL:50m; ssl_stapling on; ssl_stapling_verify on; add_header Strict-Transport-Security "max-age=31536000;"; # Forward to meteor server $ location / { proxy_pass http://localhost:3000; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } location ~ /.well-known { allow all; } } |
