title: MONGO_URL for running multiple Meteor apps on one server
body: <p>I have one Meteor application running on my Ubuntu server (Digital Ocean). I use Meteor Up (MUP) to deploy and keep the app running. Everything works fine.</p>
  
  <p>However, when I try to deploy a second app on the same server, something goes wrong in connecting to the MongoDB. I get a long and unreadable error message that starts "Invoking deployment process: FAILED" and then ends with</p>
  
  <pre><code>Waiting for MongoDB to initialize. (5 minutes)
  connected
  myapp start/running, process 25053
  Waiting for 15 seconds while app is booting up
  Checking is app booted or not?
  myapp stop/waiting
  myapp start/running, process 25114
  </code></pre>
  
  <p>And the app refuses to run. I have tried a number of things to fix this and will edit this post if more info is requested, but I'm not sure what's relevant. Essentially I don't understand the Error message, so I need to know what the heck is going on?</p>
  
  <p>EDIT:
  I want to add that my app runs fine if I go into the project folder and use the "meteor" command.  Everything runs as expected.  It is only when I try to deploy it for long-term production mode with MUP that I get this error.</p>
  
  <p>EDIT:
  I moved on to trying mupx instead of mup.  This time I can't even get past the installation process, I get the following error message:</p>
  
  <pre><code>[Neal] x Installing MongoDB: FAILED
  
  -----------------------------------STDERR-----------------------------------
  Error response from daemon: no such id: mongodb
  Error: failed to remove containers: [mongodb]
  Error response from daemon: Cannot start container c2c538d34c15103d1d07bcc60b56a54bd3d23e50ae7a8e4f9f7831df0d77dc56: failed to create endpoint mongodb on network bridge: Error starting userland proxy: listen tcp 127.0.0.1:27017: bind: address already in use
  </code></pre>
  
  <p>But I don't understand why! Mongod is clearly already running on port 27017 and a second application should just add a new database to that instance, correct? I don't know what I'm missing here, why MUP can't access MongoDB.</p>