e107 (v2) plugin - It provides an API that other plugins can use to add realtime capabilities to e107 (v2), specifically enabling pushing updates to open connected clients.
settings = {
scheme: 'http',
port: 30000,
host: 'herokuHost (which crashes if I write somethink)',
resource: '/socket.io',
serviceKey: 'myKey',
backend: {
port: 80,
host: 'myDomain.com',
scheme: 'http',
basePath: '', // If your e107 is in a subfolder, use this syntax: /my_folder
messagePath: '/panel/nodejs/nodejs.php'
},
debug: true,
sslKeyPath: '',
sslCertPath: '',
sslCAPath: '',
baseAuthPath: '/nodejs/',
publishUrl: 'publish',
kickUserUrl: 'user/kick/:uid',
logoutUserUrl: 'user/logout/:authtoken',
addUserToChannelUrl: 'user/channel/add/:channel/:uid',
removeUserFromChannelUrl: 'user/channel/remove/:channel/:uid',
addChannelUrl: 'channel/add/:channel',
removeChannelUrl: 'channel/remove/:channel',
setUserPresenceListUrl: 'user/presence-list/:uid/:uidList',
addAuthTokenToChannelUrl: 'authtoken/channel/add/:channel/:uid',
removeAuthTokenFromChannelUrl: 'authtoken/channel/remove/:channel/:uid',
toggleDebugUrl: 'debug/toggle',
contentTokenUrl: 'content/token',
publishMessageToContentChannelUrl: 'content/token/message',
extensions: [],
clientsCanWriteToChannels: false,
clientsCanWriteToClients: false,
transports: ['websocket', 'flashsocket', 'htmlfile', 'xhr-polling', 'jsonp-polling', 'polling'],
jsMinification: true,
jsEtag: true,
gzip: true,
logLevel: 1
};
scheme: 'http',
port: 30000,
host: 'herokuHost (which crashes if I write somethink)',
resource: '/socket.io',
serviceKey: 'myKey',
backend: {
port: 80,
host: 'myDomain.com',
scheme: 'http',
basePath: '', // If your e107 is in a subfolder, use this syntax: /my_folder
messagePath: '/panel/nodejs/nodejs.php'
},
debug: true,
sslKeyPath: '',
sslCertPath: '',
sslCAPath: '',
baseAuthPath: '/nodejs/',
publishUrl: 'publish',
kickUserUrl: 'user/kick/:uid',
logoutUserUrl: 'user/logout/:authtoken',
addUserToChannelUrl: 'user/channel/add/:channel/:uid',
removeUserFromChannelUrl: 'user/channel/remove/:channel/:uid',
addChannelUrl: 'channel/add/:channel',
removeChannelUrl: 'channel/remove/:channel',
setUserPresenceListUrl: 'user/presence-list/:uid/:uidList',
addAuthTokenToChannelUrl: 'authtoken/channel/add/:channel/:uid',
removeAuthTokenFromChannelUrl: 'authtoken/channel/remove/:channel/:uid',
toggleDebugUrl: 'debug/toggle',
contentTokenUrl: 'content/token',
publishMessageToContentChannelUrl: 'content/token/message',
extensions: [],
clientsCanWriteToChannels: false,
clientsCanWriteToClients: false,
transports: ['websocket', 'flashsocket', 'htmlfile', 'xhr-polling', 'jsonp-polling', 'polling'],
jsMinification: true,
jsEtag: true,
gzip: true,
logLevel: 1
};
@lonalore There it is
The heroku port is dynamic so I was using something like env.PORT, I added 30000 as static port just to test
not sure if right behaviour, plus I get invalid namespace on my e107 ajax requests
There is only 2 params I´ve not played with, use CDN and Resource ("/socket.io")
When I try to send a notification trought the notification plugin, seems that the node-js receives the request (a POST) but nothing more happens
scheme: 'http',
port: process.env.PORT || 80,
host: process.env.HOST || "peaceful-citadel-77977.herokuapp.com",
resource: '/socket.io',
serviceKey: '',
backend: {
port: 80,
host: 'yourdomain.com',
scheme: 'http',
basePath: '',
messagePath: '/panel/nodejs/nodejs.php'
},
I´ll try to set it up on another nodejs hosting, I thinkg the problem may be with heroku itself
not sure if its solved now
:)