Deploying Meteor 1.6.x and 1.8.x applications on the same server

Hi,
I have a Digital Ocean server with some Meteor applications happily deployed using mup (with let’s encrypt included).
Now I developed another Meteor application using the latest version 1.8.0.1.

I created a mup.js configuration file similar to my previous deployment made for 1.6.x:

  "servers": {
    "one": {
      "host": "1.2.3.4",
      "username": "root",
      "password": "password"
    }
  },
  "app": {
    "name": "my-app",
    "path": "../.",
    "servers": {
      "one": {}
    },
    "buildOptions": {
      "serverOnly": true
    },
    "env": {
      "ROOT_URL": "https://subdomain.host.com",
      "MONGO_URL": "mongodb://mongodb:27017/my-app",
      "PORT": 32778,
      "VIRTUAL_HOST": "mypp.domain.com",
      "HTTPS_METHOD": "redirect",
      "HTTP_FORWARDED_COUNT": 1,
      "LETSENCRYPT_HOST": "myapp.domain.com",
      "LETSENCRYPT_EMAIL": "team@domain.com"
    },
    "docker": {
      "image": "abernix/meteord:node-8.9.3-base",
      "args": [
        "--link=mongodb:mongodb"
      ]
    },
    "enableUploadProgressBar": true,
    "deployCheckWaitTime": 120,
    "type": "meteor"
  },
  "mongo": {
    "port": 27017,
    "version": "3.4.1",
    "servers": {
      "one": {}
    }
  },
  "proxy": {
    "domains": "myapp.domain.com",
    "ssl": {
      "letsEncryptEmail": "team@domain.com",
      "forceSSL": true
    }
  }
}

Can I use this or do I need to change something? How?

Thanks

Massimo

In my opinion it will remain the same. You just need to change your DNS & mongodb paths. Thats all I can think of. One thing to add here is the version of mongodb. As Meteor uses Mongodb version 4, so do check that

I need the same options too.
Could example for mup.js config for the second?
Difference mongo version 3.6x

My question is if I set mongo 3.6 as minimum requirement for minimongo compatibility, will mup create a second container for mongo (so all the rest can keep working on mongo 3.4)?

In that case I suppose that the mongo port should be changed too (27017 is already busy on mongo 3.4)

Can anyone confirm that?

I guess abernix docker image should be updated to 8.11.2 base.

Has anyone experince with 1.6 and 1.8 on the same server?

In the future it will work that way, but right now all of the apps on the server share the Mongo server. Besides that, most other aspects of the apps are independent.

1 Like

What if I use mup to deploy just the meteor app without mongo and I manually set up a docker container with mongo 4.x on it? Is that possible? Any ideas how to do it?