web/cryptpad
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

drop support for 'websocketPath' and 'useExternalWebsocket' configuration points

Browse Source
This commit is contained in:
ansuz
2019-12-23 18:23:50 -05:00
parent 97bc793ca8
commit a8b363dba0
2 changed files with 10 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
config/config.example.js
View File

@@ -97,15 +97,17 @@ module.exports = {
httpUnsafeOrigin: domain,
/* your server's websocket url is configurable
* (default: '/cryptpad_websocket')
/* Your CryptPad server will share this value with clients
* via its /api/config endpoint.
*
* websocketPath can be relative, of the form '/path/to/websocket'
* or absolute, specifying a particular URL
* If you want to host your API and asset servers on different hosts
* specify a URL for your API server websocket endpoint, like so:
* wss://api.yourdomain.com/cryptpad_websocket
*
* 'wss://cryptpad.fr:3000/cryptpad_websocket'
* Otherwise, leave this commented and your clients will use the default
* websocket (wss://yourdomain.com/cryptpad_websocket)
*/
websocketPath: '/cryptpad_websocket',
//externalWebsocketPath: 'wss://api.yourdomain.com/cryptpad_websocket
/* CryptPad can be configured to send customized HTTP Headers
* These settings may vary widely depending on your needs