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.
Hi all, are your meteor up deploys working normally ? All my deploys fail when using node 14, they can't connect to the local mongo instance on 127.0.0.1:27017 . I'm documenting my attempts at solving this in the issue #1303
I have an app that has 2 domains
in "proxy.domains"
and it works fine
But google / fb auth
But google / fb auth
cause it redirects to the "main" domain the one that set in ROOT_URL
Is there a way around it, other than create 2 docker instances with correct ROOT_URL?
I'm using image: "zodern/meteor:latest", but I think all images requite ROOT_URL
so you need one token per domain and switch the auth params depending on your url ?
so you need one token per domain and switch the auth params depending on your url ?
Well when I call Meteor.loginWithGoogle it creates redirect_url to the domain set in ROOT_URL
And looks like it is set here https://github.com/meteor/meteor/blob/4c293d329c9c24acd0c001afad6bcb6d2a4932d0/packages/oauth/oauth_common.js#L3
so you can't redirect to another domain
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
can someone help resolve this?
