You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The wiki page for Parse LiveQuery proposes a setup for a scalable live query. However, when separating the live query server from the parse server it is important to specify at least appId, masterKey and serverURL. If this information is missing the live query server will start up and allow connections but will silently not push any changes to the clients. For me the only way to find that out was to dig through the code. At the moment I could not even find documentation that these additional options exist.
A working setup looks like this:
var express = require('express');
var ParseServer = require('parse-server').ParseServer;
var app = express();
var port = process.env.PORT;
var httpServer = require('http').createServer(app);
httpServer.listen(port, function() {
console.log('live query server running on port ' + port + '.');
});
ParseServer.createLiveQueryServer(httpServer, {
appId: process.env.APP_ID,
masterKey: process.env.MASTER_KEY,
serverURL: process.env.SERVER_URL,
redisURL: process.env.REDIS_URL
});
I cannot edit the wiki page, but I believe it would be helpful if this information would be integrated into the documentation.
The text was updated successfully, but these errors were encountered:
The wiki page for Parse LiveQuery proposes a setup for a scalable live query. However, when separating the live query server from the parse server it is important to specify at least
appId
,masterKey
andserverURL
. If this information is missing the live query server will start up and allow connections but will silently not push any changes to the clients. For me the only way to find that out was to dig through the code. At the moment I could not even find documentation that these additional options exist.A working setup looks like this:
I cannot edit the wiki page, but I believe it would be helpful if this information would be integrated into the documentation.
The text was updated successfully, but these errors were encountered: