Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 12 03:30
    productiveme commented #974
  • May 11 13:47
    ivan133 opened #1317
  • May 05 00:39
    julianspink opened #1316
  • May 04 01:51
    roeurbnavy commented #1314
  • May 03 18:35
    Frustrated-Programmer commented #1141
  • May 02 05:29
    RobGordon406 opened #1315
  • Apr 28 16:56
    Chronosms commented #1314
  • Apr 28 02:16
    roeurbnavy opened #1314
  • Apr 28 02:09
    phanchanra opened #1313
  • Apr 23 15:30
    paomosca opened #1312
  • Apr 20 19:45
    zodern synchronize #1270
  • Apr 20 19:45

    zodern on release-1.6

    Release 1.6.0-beta.3 (compare)

  • Apr 20 19:44
    zodern synchronize #1270
  • Apr 20 19:44

    zodern on release-1.6

    Release 1.6.0-beta.2 Merge branch 'release-1.6' of h… (compare)

  • Apr 20 19:36
    zodern synchronize #1270
  • Apr 20 19:36

    zodern on release-1.6

    Fix Meteor 2.6 compatilibity Release 1.5.6 Fix initializing mongo replica … and 36 more (compare)

  • Apr 20 19:29

    zodern on v1.5.8

    (compare)

  • Apr 20 18:49

    zodern on master

    Release 1.5.8 (compare)

  • Apr 18 23:57

    zodern on master

    Fix importing uuid (compare)

  • Apr 18 23:38

    zodern on master

    Release 1.5.8-beta.1 Update uuid (compare)

Erik Demaine
@edemaine
In case anyone would like an example configuration for a multiple-machine deployment, here is one, along with description / recommended configuration.
Laurent Roger
@lc3t35
thank you @edemaine, did you also study how to upscale mongo ?
Grzegorz Pociejewski
@pociej
hi, is here anyone who can help me with SSL setup ?
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

      ------------------------------------------------------------------------------```
Laurent Roger
@lc3t35
as it said, port is already allocated
do you have another ng’ox or apache2 running on your host or another docker ?
(« another nginx »)
Grzegorz Pociejewski
@pociej
@lc3t35 thx for reply but there is no ngix at least not one run by me. Here is what is running there :
➜ 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
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 ?
Grzegorz Pociejewski
@pociej
Ok after i stop the app config proxy and them redeploy it seems to be running ( at least no error )
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 ?
Laurent Roger
@lc3t35
what is the error message ?
zodern
@zodern
I released mup-node 0.8 today. This release adds support for production debugging. Run mup node debug, and you can connect your local Node devtools, for example those in Chrome, to your Node app running on the server.
Slind14
@Slind14
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 Error response from daemon: Dockerfile parse error line 13: ARG requires exactly one argument
or adding them to the node start command
Richard Marks
@TheRichardMarks_gitlab
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.
Fred-J
@Fred-J
Hello, When mup setup --verbose runs on Windows 10 Power Shell, it gives path\to\mup.ps1 is not digitally signed. Do I need to change Windows PowerShell execution policies? The second question is do I need to use mup.cmd setup or that ".cmd" only applies to mup.cmd init?
Eric Priou
@erixtekila
Hi,
Could somebody share a post.mongo.start hook that access mongo via its shell. Thanks
Laurent Roger
@lc3t35
can you detail Erik ?
Eric Priou
@erixtekila
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);
    }
  }
conorstrejcek
@conorstrejcek
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.
conorstrejcek
@conorstrejcek
@djbelieny Did you ever get more information on updating the nginx-proxy docker image?
Rob Gordon
@robgordon_gitlab

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
@conorstrejcek
@robgordon_gitlab If you are using the proxy, are you able to share nginx logs?
Fred-J
@Fred-J
How to modify the proxy nginx-config which is generated by mup? "mup proxy nginx-config" shows it.
Rob Gordon
@robgordon_gitlab
@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 :)
Ghost
@ghost~5cfd437dd73408ce4fc29676
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
fmatheus
@fmatheus_gitlab
Hi, hope this is the right place to ask, npm is hanging in the middle of npm install --unsafe-perms inside docker, outside seens to work fine. Any hints?
seems to be on the 'extract:reify' (npm 6) or 'inflate:xtend' (npm 7) so registry http did not worked
fmatheus
@fmatheus_gitlab
reify is only installed by mup script, npm install --unsafe-perms works fine in my app inside zodern/meteor image when I download it, but hangs with in the same image with mup script, maybe the problem is it trying to install meteor 2.2 deps?
fmatheus
@fmatheus_gitlab
changing to meteor 2.2.3 moves to hang while extracting fibers
fmatheus
@fmatheus_gitlab
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.
Ghost
@ghost~5cfd437dd73408ce4fc29676
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
Laurent Roger
@lc3t35
seems to be solved ;)
James "Rusty" Haner
@JRustyHaner
Good morning all
Ivan
@ivan133
Hey guys
I have an app that has 2 domains
in "proxy.domains"
and it works fine
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
Laurent Roger
@lc3t35
redirect url is defined on google side when you create the auth token, no ?
so you need one token per domain and switch the auth params depending on your url ?
Ivan
@ivan133

redirect url is defined on google side when you create the auth token, no ?

Yes

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

Laurent Roger
@lc3t35
you can define and use : process.env.MOBILE_ROOT_URL (replace meteor_runtime_config.ROOT_URL; if defined)