https://meteor-up.com/docs.html#swarm says that swarm is required for load balancing and zero-downtime deploys, while https://zodern.me/posts/meteor-up-1-5/ seems to suggest that this can be done just with nginx proxy. Which is right?
If you use let's encrypt, the proxy can only be run on one server. If you want to run the proxy on multiple servers, you can create the certificates from a different source and have Meteor Up upload them to each server. For one app that I want multiple load balancers for, I use https://support.cloudflare.com/hc/en-us/articles/115000479507-Managing-Cloudflare-Origin-CA-certificates.
For medium scale deploys of a production app you might want to:
- If you use Let's encrypt, have one server with the proxy. If your Meteor app uses a lot of CPU or you have a large number of requests per second you might want this on a separate server. Mup 1.6 will likely support high availability for the proxy when using a floating IP address and multiple servers, but right now it is a single point of failure.
- Use Atlas or another Mongo hosting service, or run a replica set yourself
- Run the app on 3+ servers for high availability and spreading the load
- Optionally use a private docker registry for faster deploys: http://meteor-up.com/docs.html#private-docker-registry
I'm looking to support a static site at the domain (e.g. example.com) on an AWS EC2 instance.
I'd like to run the meteor app at a subdomain for the same domain (e.g. mysubdomain.example.com)
Currently I have the mysubdomain.example.com working and I'd like some help with getting the static site working. Can anybody provide an example mup.js file that does what I'm looking for? Do I need to build a docker image with my static site?
I'd like to run the meteor app at a subdomain for the same domain (e.g. mysubdomain.example.com)
Currently I have the mysubdomain.example.com working and I'd like some help with getting the static site working. Can anybody provide an example mup.js file that does what I'm looking for? Do I need to build a docker image with my static site?
Thanks in advance for everyone's help
I had considered building a plugin for static websites, but I've switched to using Netlify or similar services. Would you mind sharing why you want to host your static site on the server instead of using a service? If there is enough interest I might still build the plugin.
These would be the two easiest options:
- Use https://www.npmjs.com/package/mup-docker-deploy with a custom dockerfile
- Create a simple node server (maybe with express and the static middleware) to serve the static files and deploy with https://www.npmjs.com/package/mup-node
I didn't want to have the static website and meteor site on two different servers or services. Trying to keep everything on one EC2 instance. Reading the docs a bit more, can I use env PORT to solve my problem? If I set env PORT for the app to something other than 80 (say 5000 like the example in the doc), would subdomain work to connect to that port automatically? I could then use my current nginx setup for the static website on the server that binds to port 80/443
In case anyone would like an example configuration for a multiple-machine deployment, here is one, along with description / recommended configuration.
Im trying to run mup proxy setup but i got
```Started TaskList: Setup proxy
[46.101.130.237] - Setup Environment
[46.101.130.237] - Setup Environment: SUCCESS
[46.101.130.237] - Pushing the Startup Script
[46.101.130.237] - Pushing the Startup Script: SUCCESS
[46.101.130.237] - Pushing Nginx Config Template
[46.101.130.237] - Pushing Nginx Config Template: SUCCESS
[46.101.130.237] - Pushing Nginx Config
[46.101.130.237] - Pushing Nginx Config: SUCCESS
[46.101.130.237] - Cleaning Up SSL Certificates
[46.101.130.237] - Cleaning Up SSL Certificates: SUCCESS
[46.101.130.237] - Copying SSL Certificate Bundle
[46.101.130.237] - Copying SSL Certificate Bundle: SUCCESS
[46.101.130.237] - Copying SSL Private Key
[46.101.130.237] - Copying SSL Private Key: SUCCESS
[46.101.130.237] - Setup SSL Certificates for Domains
[46.101.130.237] - Setup SSL Certificates for Domains: SUCCESS
[46.101.130.237] - Configure Nginx Upstream
[46.101.130.237] - Configure Nginx Upstream: SUCCESS
Started TaskList: Start proxy
[46.101.130.237] - Start proxy
[46.101.130.237] x Start proxy: FAILED
------------------------------------STDERR------------------------------------
Error response from daemon: endpoint mup-nginx-proxy not found
Error response from daemon: network mup-proxy not found
Error: No such container: mup-nginx-proxy-letsencrypt
Error response from daemon: endpoint mup-nginx-proxy-letsencrypt not found
Error response from daemon: network mup-proxy not found
docker: Error response from daemon: driver failed programming external connectivity on endpoint mup-nginx-proxy (057cfe2e00d4b1ee883bd96e44eee00af88d5afc490dfc4b33bb724954e5a323): Bind for 0.0.0.0:80 failed: port is already allocated.
------------------------------------STDOUT------------------------------------
mup-nginx-proxy
Removed mup-nginx-proxy
Removed mup-nginx-proxy-letsencrypt
latest: Pulling from jrcs/letsencrypt-nginx-proxy-companion
Digest: sha256:c2eaeb6a04620732d30003fecdf9c3ae81c2b7f838fb8485c6f2c21366bffabd
Status: Image is up to date for jrcs/letsencrypt-nginx-proxy-companion:latest
docker.io/jrcs/letsencrypt-nginx-proxy-companion:latest
Using default tag: latest
latest: Pulling from jwilder/nginx-proxy
Digest: sha256:4116f2b6fb9b2a41d94149e8261c81ebbfd96aa84882d87f19c45e00a7c3c221
Status: Image is up to date for jwilder/nginx-proxy:latest
docker.io/jwilder/nginx-proxy:latest
Pulled jwilder/nginx-proxy and jrcs/letsencrypt-nginx-proxy-companion
d3ecc6eacb03a35e3e49075c957b4fc16f8f42cbb89acecdf00cb331ff20875f
------------------------------------------------------------------------------```
do you have another ng’ox or apache2 running on your host or another docker ?
(« another nginx »)
➜ stage git:(stage) ✗ mup docker ps
[46.101.130.237] docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
18ca9aafb793 mup-app:latest "/bin/sh -c 'bash $M…" 44 hours ago Up 44 hours 0.0.0.0:80->80/tcp app
1561a2cec1a3 mongo:3.4.1 "/entrypoint.sh mong…" 7 weeks ago Up 11 days 127.0.0.1:27017->27017/tcp mongodb
[46.101.130.237] docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
18ca9aafb793 mup-app:latest "/bin/sh -c 'bash $M…" 44 hours ago Up 44 hours 0.0.0.0:80->80/tcp app
1561a2cec1a3 mongo:3.4.1 "/entrypoint.sh mong…" 7 weeks ago Up 11 days 127.0.0.1:27017->27017/tcp mongodb
so indeed there is app running on port 80
but i expected mup to manage things. Should i stop app cntainer then run proxy and redeploy ?
but still i see invalid cert error while im sure certificate is ok, should i go there and place certificate related files somwhere in container ?
Hi @zodern do you know if there is a way to set an environment variable with multiple args? E.g. for nodejs diagnostics this is required:
NODE_OPTIONS: '--report-uncaught-exception --report-on-fatalerror --report-on-signal --report-signal=SIGUSR2 --report-filename=./meteor-app-diagnostic-report.json --report-directory=/tmp'
If done through mup it fails with
NODE_OPTIONS: '--report-uncaught-exception --report-on-fatalerror --report-on-signal --report-signal=SIGUSR2 --report-filename=./meteor-app-diagnostic-report.json --report-directory=/tmp'
If done through mup it fails with
Error response from daemon: Dockerfile parse error line 13: ARG requires exactly one argument
or adding them to the node start command
Hello everyone. I have a bit of an issue. I've been hired to update an app that is pretty active and in production. I'm faced with redeploying updates to the app, it was learned that mup was used to deploy the app, however the original deployment mup.js file is no longer available. I have root ssh access to the production server. Is there any way for me to reverse-engineer/dump the mup.js config details on the production server so that I can recreate the deployment to match the current configuration? Or do I have to start over from scratch? There are multiple apps being run through mup on this server, and downtime needs to be at a minimum.
Yep. I would like to launch a ssh command, after the local mongo db has started. BTW, the plugin API is not really documented and I have hard time to figure how to get into mongo from it
hooks": {
"post.mongo.start" (api)
{
const config = api.getConfig();
console.log(config);
}
}
Hey, I had a quick question about the docker image which meteor-up uses for the proxy. Is it possible to update to a newer version of this image using the
mup CLI, or is there an accepted way to do this? I mainly want to keep nginx up to date without interfering with the normal mup process, so I've been avoiding manually updating the image.
Hi - in need of assistance - been using mup for 4+ years. Love it.
But I'm completely at a loss as to why I'm getting a 503 Service Temporarily Unavailable. (Am trying to re-release an existing working app to a new Digital Ocean droplet)
mup status looks like everything has deployed perfectly. Any suggestions?
Meteor version 1.8.2.
image: 'zodern/meteor:root'.
@conorstrejcek @Fred-J Thanks for your responses. As mentioned, this was an existing application that had successfully been deployed perhaps a dozen times over the last 12 months. I'm not sure why I was getting that error, nor why it finally deployed without an error; very frustrating but as of Mar 08 it's been uploaded :)
Hi all, I've created a github workflow to upload my open source app to digital ocean with mup directly in a github vm. It lets me deploy faster (my upload speed at home is terrible) and rollback changes on github from a mobile phone (useful for indies). So i though i'd share the file : https://github.com/renanlecaro/simpletextnet/blob/master/.github/workflows/main.yml
seems to be on the 'extract:reify' (npm 6) or 'inflate:xtend' (npm 7) so registry http did not worked
Looks like the problem isn't of above, npm is just eating the error:
meteor build (2.2.x) for some reason is generating a bundle/programs/server/package.json with "source-map-support": "https://github.com/meteor/node-source-map-support/tarball/1912478769d76e5df4c365e147f25896aee6375e" instead of package version, editing it to "source-map-support": "0.5.20" workaround the issue.
