Added multi-app support in DatabaseAdapter.js

[jamiechapman]

When creating multiple instances of ParseServer to connect to different databases using a single server, the databaseURI was getting overwritten by the last defined connection string (issue: #116).

This patch stores each connection string by appId so that they're not overwritten when creating new ParseServer objects.

This patch then allows the user to host multiple apps on the same server like this:-

var api = new ParseServer({appId:'app1', 'databaseUri:'mongodb://.../database1', ...});
var api2 = new ParseServer({appId:'app2', 'databaseUri:'mongodb://.../database2', ...});

app.use('/app1/parse', api);
app.use('/app2/parse', api2);

[gfosco]

Sure, looks good. Thanks. 👍

[ucoker]

It's worked.
My code:

• index.js

var express = require('express');
var ParseServer = require('parse-server').ParseServer;
var app = express();

var api = new ParseServer({
  databaseURI: 'mongodb://localhost:27017/dev', // Connection string for your MongoDB database
  cloud: '/home/parse/parse-server/cloud/main.js', // Absolute path to your Cloud Code
  appId: 'bb',
  masterKey: 'your-master-key', // Keep this key secret!
  serverURL: 'http://localhost:1337/parse' // Don't forget to change to https if needed
});
app.use('/parse/bb', api);

var api2 = new ParseServer({
  databaseURI: 'mongodb://localhost:27017/dev2', // Connection string for your MongoDB database
  cloud: '/home/parse/parse-server/cloud/main.js', // Absolute path to your Cloud Code
  appId: 'cc',
  masterKey: 'your-master-key', // Keep this key secret!
  serverURL: 'http://localhost:1337/parse' // Don't forget to change to https if needed
});
app.use('/parse/cc', api2);

app.listen(1337, function() {
  console.log('parse-server-example running on port 1337.');
});

• screenshot on parse-dashboard
  

  Thanks.
  @jamiechapman

[flovilmart]

It Wont Work With cloud code....

[ralphilius]

@flovilmart Would it work if I use pm2 to set up multiple instances in which each one has separate cloud code url?

[ucoker]

@ralphilius You can try this.

├── parse-server
│   ├── apps
│   │   ├── app1
│   │   │   └── cloud
│   │   │       └── main.js
│   │   └── app2
│   │       └── cloud
│   │           └── main.js
│   ├── ecosystem.json
│   ├── index.js
│   ├── logs
│   ├── node_modules [259 entries exceeds filelimit, not opening dir]
│   ├── package.json
│   └── parse-dashboard-config.json

• index.js

var express = require('express');
var ParseServer = require('parse-server').ParseServer;
var moment = require('moment');

var app = express();

var api_app1 = new ParseServer({
  databaseURI: 'mongodb://localhost:27017/dbApp1', // Connection string for your MongoDB database
  cloud: '/home/parse/parse-server/apps/app1/cloud/main.js', // Absolute path to your Cloud Code
  appId: 'app1',
  masterKey: 'the_masterKey', // Keep this key secret!
  serverURL: 'http://localhost:1337/parse' // Don't forget to change to https if needed
});
app.use('/parse/app1', api_app1);

var api_app2 = new ParseServer({
  databaseURI: 'mongodb://localhost:27017/dbApp2', // Connection string for your MongoDB database
  cloud: '/home/parse/parse-server/apps/app2/cloud/main.js', // Absolute path to your Cloud Code
  appId: 'app2',
  masterKey: 'the_masterKey', // Keep this key secret!
  serverURL: 'http://localhost:1337/parse' // Don't forget to change to https if needed
});
app.use('/parse/app2', api_app2);

app.listen(1337, function() {
  var dateNow = moment(new Date()).format("YYYY-MMM-D HH:mm --> ");
  console.log(dateNow + 'parse-server running on port 1337.');
});

• parse-dashboard-config.json

{
    "apps": [{
        "serverURL": "https://youdomain.com/parse/app1",
        "appId": "app1",
        "masterKey": "the_masterKey",
        "appName": "app1"
    },{
        "serverURL": "https://youdomain.com/parse/app2",
        "appId": "app2",
        "masterKey": "the_masterKey",
        "appName": "app2"
    }],

    "users": [{
        "user":"user1",
        "pass":"pass"
    },{
        "user":"user2",
        "pass":"pass"
    }]
}

• ecosystem.json

{
    "apps" : [{
        "name"        : "parse-apps",
        "script"      : "/usr/bin/node",
        "watch"       : true,
        "merge_logs"  : true,
        "cwd"         : "/home/parse/parse-server",
        "args"        : "index.js"
    },{
    "name"        : "parse-dashboard",
    "script"      : "/usr/bin/parse-dashboard",
    "watch"       : true,
    "merge_logs"  : true,
    "cwd"         : "/home/parse/parse-server",
    "args"         : "--config parse-dashboard-config.json --mountPath /dashboard"
    }]
}

then, pm2 start ecosystem.json
Hope to help you.

[ralphilius]

Thanks for verifying @ucoker
This is similar to what I use. I am using 2 pm2 instances with different env variables and nginx as http proxy

[flovilmart]

Your clous code won't work

[n00r]

how to create dynamically ......like back4app.

[chderen]

you can run with parse-server-example or other methods multi apps instance.
by running the new ParseServer() function with the correct params.
i don't know about cloud code, but other functionality works grate.

there is one problem, creating more then 10 apps will brake the run time, because at ParseServer.js there is a listening to event process.on('uncaughtException', ...) which can run only ten times.
my solution was to create edit the source at that point.

the difference between the apps is by the http request credentials.

good lock!

[wujohns]

When you create multi app instance in this way,The param global.Parse.Cloud will be overwritten util all instances created.I agree @flovilmart

[wujohns]

The feature for multi app instance is uncompleted in parse-server 2.3.1

[walxlgf]

LiveQuery does not work it this way. Any body can solve it?