[SelfSolved] MONGO_URL being ignored when deploying app

deployment
1

Hi all, can someone spot what is wrong with the following ?
I have:

  • my-app-1
  • my-app-2

running on the same server. my-app-1 created a

  • my-db-1

I want my-app-2 to use my-db-1.
my-app-1 was deployed with a:

  • MONGO_URL: 'mongodb://localhost/meteor’
    and appears in docker as
  • “mongodb” 127.0.0.1:27017->27017/tcp

my-app-2 was deployed with a MONGO_URL of:

  • mongodb://localhost/meteor
  • mongodb://localhost:27017/meteor
  • mongodb://mongodb:27017/meteor
  • mongodb://localhost:27017
  • mongodb://mongodb:27017/my-app-1 (db name in mongo is same as app name apparent when I ran “show dbs”)
  • mongodb://localhost:27017/my-app-1

Nothing works

//EDIT: I went into the my-app-2 image and ran “env”, the MONGO_URL is set to mongodb://mongo:27017/my-app-2, how can this be possible since I never specified something like this and what can I do to fix this? The mup tool doesn’t seem to be doing it’s job
//EDIT2: also, the MONGO_URL from the my-app-1 container is set to mongodb://mongo:27017/my-app-1, which is not at all what I set in its deploy json

2

Made it!

I had to (read the damn documentation) put in mup.js the following:

    docker: {
      image: 'abernix/meteord:node-8.4.0-base',
		args: [  // only the args part, not the image which is by default
        '--link=mongodb:mongodb'
		]
    },

then remove

  mongo: {
    version: '3.4.1',
    servers: {
      one: {}
    }
  }

and the correct MONGO_URL is:

MONGO_URL: 'mongodb://mongodb:27017/my-app-1,

1 Like