Multiple apps on one server

[samarthagarwal]

Hi. I am trying to have multiple apps on one single parse-server deployment. How is it possible?
Since each app will have different app ids, Is it still possible for apps to coincide?

[samarthagarwal]

Is connecting each app to a separate mongodb database, a good way to go?

[christianmarth]

I'm looking at doing the same thing, thinking will need to create a new database and instance of ParseServer for each app and map this to a different path, maybe something like this

var app1 = new ParseServer({
  databaseURI: 'mongodb://localhost:27017/app1',
  cloud: '/home/app1/cloud/main.js', // Provide an absolute path
  appId: 'myAppId',
  masterKey: 'mySecretMasterKey',
  fileKey: 'optionalFileKey'
});

// Serve the Parse API on the /parse URL prefix
app.use('/app1', app1);

var app2 = new ParseServer({
  databaseURI: 'mongodb://localhost:27017/app2',
  cloud: '/home/app2/cloud/main.js', // Provide an absolute path
  appId: 'myAppId',
  masterKey: 'mySecretMasterKey',
  fileKey: 'optionalFileKey'
});

// Serve the Parse API on the /parse URL prefix
app.use('/app2', app2);

[samarthagarwal]

So if the client SDK connects to the url /parse, which parse-server instance will actually work? I don't think we should mount both to the same endpoint.

[christianmarth]

Sorry, i meant also change the url so you have /app1 /app2

[samarthagarwal]

Do we have any open source dashboard like project that when used with parse-server can give us a Parse like dashboard? Is someone developing it? I am willing to write one myself.

[christianmarth]

Have a look at #3

I'm interested in contributing to a dashboard as well, for most of my apps, I've just written a custom CRUD dashboard in Javascript

[gfosco]

Right now the main hurdle for multi-app support will be cloud code. The middleware which creates Parse.Cloud.define/etc will need to be updated similarly to #139 to somehow support separate cloud code initialization. Right now it's easy enough to run multiple from the database side... I'm going to close this for now but hope to see the server hosting multiple apps and cloud code in the not-too-distant future.

[jamiechapman]

@gfosco funnily enough I was playing around with the middleware which deals with the Cloud Code functions yesterday (fairly similar to #139).

I managed to get the functions loaded up for different apps— but the brick wall in the end was the handleCloudFunction method inside functions.js. It's providing difficult to get the current appId at this stage of the request; for some reason req.body at that stage appears to be empty (even though I don't think it should be as bodyParser should have parsed it as JSON like it would in classes.js) — thus exposing _ApplicationId and allowing me to select the right Parse.Cloud function.

The other issue is the Parse library itself appears to be a global variable, so Parse.applicationId only returns the last defined application — and I guess this probably has a knock-on effect within the Cloud Code itself (e.g. when issuing queries and such?). So I guess that potentially would need some significant refactoring too?

[baluragala]

Does anyone has a workaround for multiple apps with different cloud codes? I have been trying to figure out a way to implement. any quick thoughts please?

[christianmarth]

Best solution currently is to just create two instances of parse server for now...

[kilabyte]

You can run the multi instance all in one index and use nodemon to manage the service when for when you makes changes or add another instance.