|
|
|
@ -1,67 +1,110 @@
|
|
|
|
|
/*
|
|
|
|
|
globals module
|
|
|
|
|
*/
|
|
|
|
|
var _domain = 'http://localhost:3000/';
|
|
|
|
|
/* globals module */
|
|
|
|
|
|
|
|
|
|
/* DISCLAIMER:
|
|
|
|
|
|
|
|
|
|
There are two recommended methods of running a CryptPad instance:
|
|
|
|
|
|
|
|
|
|
// You can `kill -USR2` the node process and it will write out a heap dump.
|
|
|
|
|
// If your system doesn't support dumping, comment this out and install with
|
|
|
|
|
// `npm install --production`
|
|
|
|
|
// See: https://strongloop.github.io/strongloop.com/strongblog/how-to-heap-snapshots/
|
|
|
|
|
1. Using a standalone nodejs server without HTTPS (suitable for local development)
|
|
|
|
|
2. Using NGINX to serve static assets and to handle HTTPS for API server's websocket traffic
|
|
|
|
|
|
|
|
|
|
// to enable this feature, uncomment the line below:
|
|
|
|
|
// require('heapdump');
|
|
|
|
|
We do not officially recommend or support Apache, Docker, Kubernetes, Traefik, or any other configuration.
|
|
|
|
|
Support requests for such setups should be directed to their authors.
|
|
|
|
|
|
|
|
|
|
// we prepend a space because every usage expects it
|
|
|
|
|
// requiring admins to preserve it is unnecessarily confusing
|
|
|
|
|
var domain = ' ' + _domain;
|
|
|
|
|
If you're having difficulty difficulty configuring your instance
|
|
|
|
|
we suggest that you join the project's IRC/Matrix channel.
|
|
|
|
|
|
|
|
|
|
// Content-Security-Policy
|
|
|
|
|
var baseCSP = [
|
|
|
|
|
"default-src 'none'",
|
|
|
|
|
"style-src 'unsafe-inline' 'self' " + domain,
|
|
|
|
|
"font-src 'self' data:" + domain,
|
|
|
|
|
If you don't have any difficulty configuring your instance and you'd like to
|
|
|
|
|
support us for the work that went into making it pain-free we are quite happy
|
|
|
|
|
to accept donations via our opencollective page: https://opencollective.com/cryptpad
|
|
|
|
|
|
|
|
|
|
/* child-src is used to restrict iframes to a set of allowed domains.
|
|
|
|
|
* connect-src is used to restrict what domains can connect to the websocket.
|
|
|
|
|
*/
|
|
|
|
|
module.exports = {
|
|
|
|
|
/* CryptPad is designed to serve its content over two domains.
|
|
|
|
|
* Account passwords and cryptographic content is handled on the 'main' domain,
|
|
|
|
|
* while the user interface is loaded on a 'sandbox' domain
|
|
|
|
|
* which can only access information which the main domain willingly shares.
|
|
|
|
|
*
|
|
|
|
|
* In the event of an XSS vulnerability in the UI (that's bad)
|
|
|
|
|
* this system prevents attackers from gaining access to your account (that's good).
|
|
|
|
|
*
|
|
|
|
|
* Most problems with new instances are related to this system blocking access
|
|
|
|
|
* because of incorrectly configured sandboxes. If you only see a white screen
|
|
|
|
|
* when you try to load CryptPad, this is probably the cause.
|
|
|
|
|
*
|
|
|
|
|
* PLEASE READ THE FOLLOWING COMMENTS CAREFULLY.
|
|
|
|
|
*
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* httpUnsafeOrigin is the URL that clients will enter to load your instance.
|
|
|
|
|
* Any other URL that somehow points to your instance is supposed to be blocked.
|
|
|
|
|
* The default provided below assumes you are loading CryptPad from a server
|
|
|
|
|
* which is running on the same machine, using port 3000.
|
|
|
|
|
*
|
|
|
|
|
* In a production instance this should be available ONLY over HTTPS
|
|
|
|
|
* using the default port for HTTPS (443) ie. https://cryptpad.fr
|
|
|
|
|
* In such a case this should be handled by NGINX, as documented in
|
|
|
|
|
* cryptpad/docs/example.nginx.conf (see the $main_domain variable)
|
|
|
|
|
*
|
|
|
|
|
* it is recommended that you configure these fields to match the
|
|
|
|
|
* domain which will serve your CryptPad instance.
|
|
|
|
|
*/
|
|
|
|
|
"child-src blob: *",
|
|
|
|
|
// IE/Edge
|
|
|
|
|
"frame-src blob: *",
|
|
|
|
|
httpUnsafeOrigin: 'http://localhost:3000/',
|
|
|
|
|
|
|
|
|
|
/* this allows connections over secure or insecure websockets
|
|
|
|
|
if you are deploying to production, you'll probably want to remove
|
|
|
|
|
the ws://* directive, and change '*' to your domain
|
|
|
|
|
/* httpSafeOrigin is the URL that is used for the 'sandbox' described above.
|
|
|
|
|
* If you're testing or developing with CryptPad on your local machine then
|
|
|
|
|
* it is appropriate to leave this blank. The default behaviour is to serve
|
|
|
|
|
* the main domain over port 3000 and to serve the content over port 3001.
|
|
|
|
|
*
|
|
|
|
|
* This is not appropriate in a production environment where invasive networks
|
|
|
|
|
* may filter traffic going over abnormal ports.
|
|
|
|
|
* To correctly configure your production instance you must provide a URL
|
|
|
|
|
* with a different domain (a subdomain is sufficient).
|
|
|
|
|
* It will be used to load the UI in our 'sandbox' system.
|
|
|
|
|
*
|
|
|
|
|
* This value corresponds to the $sandbox_domain variable
|
|
|
|
|
* in the example nginx file.
|
|
|
|
|
*
|
|
|
|
|
* CUSTOMIZE AND UNCOMMENT THIS FOR PRODUCTION INSTALLATIONS.
|
|
|
|
|
*/
|
|
|
|
|
"connect-src 'self' ws: wss: blob:" + domain,
|
|
|
|
|
// httpSafeOrigin: "https://some-other-domain.xyz",
|
|
|
|
|
|
|
|
|
|
// data: is used by codemirror
|
|
|
|
|
"img-src 'self' data: blob:" + domain,
|
|
|
|
|
"media-src * blob:",
|
|
|
|
|
/* httpAddress specifies the address on which the nodejs server
|
|
|
|
|
* should be accessible. By default it will listen on 127.0.0.1
|
|
|
|
|
* (IPv4 localhost on most systems). If you want it to listen on
|
|
|
|
|
* all addresses, including IPv6, set this to '::'.
|
|
|
|
|
*
|
|
|
|
|
*/
|
|
|
|
|
//httpAddress: '::',
|
|
|
|
|
|
|
|
|
|
// for accounts.cryptpad.fr authentication and cross-domain iframe sandbox
|
|
|
|
|
"frame-ancestors *",
|
|
|
|
|
""
|
|
|
|
|
];
|
|
|
|
|
/* httpPort specifies on which port the nodejs server should listen.
|
|
|
|
|
* By default it will serve content over port 3000, which is suitable
|
|
|
|
|
* for both local development and for use with the provided nginx example,
|
|
|
|
|
* which will proxy websocket traffic to your node server.
|
|
|
|
|
*
|
|
|
|
|
*/
|
|
|
|
|
//httpPort: 3000,
|
|
|
|
|
|
|
|
|
|
/* httpSafePort allows you to specify an alternative port from which
|
|
|
|
|
* the node process should serve sandboxed assets. The default value is
|
|
|
|
|
* that of your httpPort + 1. You probably don't need to change this.
|
|
|
|
|
*
|
|
|
|
|
*/
|
|
|
|
|
//httpSafePort: 3001,
|
|
|
|
|
|
|
|
|
|
module.exports = {
|
|
|
|
|
/* =====================
|
|
|
|
|
* Admin
|
|
|
|
|
* ===================== */
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* CryptPad now contains an administration panel. Its access is restricted to specific
|
|
|
|
|
* CryptPad contains an administration panel. Its access is restricted to specific
|
|
|
|
|
* users using the following list.
|
|
|
|
|
* To give access to the admin panel to a user account, just add their user id,
|
|
|
|
|
* which can be found on the settings page for registered users.
|
|
|
|
|
* Entries should be strings separated by a comma.
|
|
|
|
|
*/
|
|
|
|
|
/*
|
|
|
|
|
adminKeys: [
|
|
|
|
|
//"https://my.awesome.website/user/#/1/cryptpad-user1/YZgXQxKR0Rcb6r6CmxHPdAGLVludrAF2lEnkbx1vVOo=",
|
|
|
|
|
],
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* CryptPad's administration panel includes a "support" tab
|
|
|
|
|
* wherein administrators with a secret key can view messages
|
|
|
|
@ -76,159 +119,55 @@ module.exports = {
|
|
|
|
|
*/
|
|
|
|
|
// supportMailboxPublicKey: "",
|
|
|
|
|
|
|
|
|
|
/* =====================
|
|
|
|
|
* Infra setup
|
|
|
|
|
* ===================== */
|
|
|
|
|
|
|
|
|
|
// the address you want to bind to, :: means all ipv4 and ipv6 addresses
|
|
|
|
|
// this may not work on all operating systems
|
|
|
|
|
httpAddress: '::',
|
|
|
|
|
|
|
|
|
|
// the port on which your httpd will listen
|
|
|
|
|
httpPort: 3000,
|
|
|
|
|
|
|
|
|
|
// This is for allowing the cross-domain iframe to function when developing
|
|
|
|
|
httpSafePort: 3001,
|
|
|
|
|
|
|
|
|
|
// This is for deployment in production, CryptPad uses a separate origin (domain) to host the
|
|
|
|
|
// cross-domain iframe. It can simply host the same content as CryptPad.
|
|
|
|
|
// httpSafeOrigin: "https://some-other-domain.xyz",
|
|
|
|
|
|
|
|
|
|
httpUnsafeOrigin: domain,
|
|
|
|
|
|
|
|
|
|
/* Your CryptPad server will share this value with clients
|
|
|
|
|
* via its /api/config endpoint.
|
|
|
|
|
*
|
|
|
|
|
* 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
|
|
|
|
|
*
|
|
|
|
|
* Otherwise, leave this commented and your clients will use the default
|
|
|
|
|
* websocket (wss://yourdomain.com/cryptpad_websocket)
|
|
|
|
|
*/
|
|
|
|
|
//externalWebsocketURL: 'wss://api.yourdomain.com/cryptpad_websocket
|
|
|
|
|
|
|
|
|
|
/* CryptPad can be configured to send customized HTTP Headers
|
|
|
|
|
* These settings may vary widely depending on your needs
|
|
|
|
|
* Examples are provided below
|
|
|
|
|
*/
|
|
|
|
|
httpHeaders: {
|
|
|
|
|
"X-XSS-Protection": "1; mode=block",
|
|
|
|
|
"X-Content-Type-Options": "nosniff",
|
|
|
|
|
"Access-Control-Allow-Origin": "*"
|
|
|
|
|
},
|
|
|
|
|
|
|
|
|
|
contentSecurity: baseCSP.join('; ') +
|
|
|
|
|
"script-src 'self'" + domain,
|
|
|
|
|
|
|
|
|
|
// CKEditor and OnlyOffice require significantly more lax content security policy in order to function.
|
|
|
|
|
padContentSecurity: baseCSP.join('; ') +
|
|
|
|
|
"script-src 'self' 'unsafe-eval' 'unsafe-inline'" + domain,
|
|
|
|
|
|
|
|
|
|
/* Main pages
|
|
|
|
|
* add exceptions to the router so that we can access /privacy.html
|
|
|
|
|
* and other odd pages
|
|
|
|
|
*/
|
|
|
|
|
mainPages: [
|
|
|
|
|
'index',
|
|
|
|
|
'privacy',
|
|
|
|
|
'terms',
|
|
|
|
|
'about',
|
|
|
|
|
'contact',
|
|
|
|
|
'what-is-cryptpad',
|
|
|
|
|
'features',
|
|
|
|
|
'faq',
|
|
|
|
|
'maintenance'
|
|
|
|
|
],
|
|
|
|
|
|
|
|
|
|
/* =====================
|
|
|
|
|
* Subscriptions
|
|
|
|
|
* ===================== */
|
|
|
|
|
|
|
|
|
|
/* Limits, Donations, Subscriptions and Contact
|
|
|
|
|
*
|
|
|
|
|
* By default, CryptPad limits every registered user to 50MB of storage. It also shows a
|
|
|
|
|
* subscribe button which allows them to upgrade to a paid account. We handle payment,
|
|
|
|
|
* and keep 50% of the proceeds to fund ongoing development.
|
|
|
|
|
/* We're very proud that CryptPad is available to the public as free software!
|
|
|
|
|
* We do, however, still need to pay our bills as we develop the platform.
|
|
|
|
|
*
|
|
|
|
|
* You can:
|
|
|
|
|
* A: leave things as they are
|
|
|
|
|
* B: disable accounts but display a donate button
|
|
|
|
|
* C: hide any reference to paid accounts or donation
|
|
|
|
|
* By default CryptPad will prompt users to consider donating to
|
|
|
|
|
* our OpenCollective campaign. We publish the state of our finances periodically
|
|
|
|
|
* so you can decide for yourself whether our expenses are reasonable.
|
|
|
|
|
*
|
|
|
|
|
* If you chose A then there's nothing to do.
|
|
|
|
|
* If you chose B, set 'allowSubscriptions' to false.
|
|
|
|
|
* If you chose C, set 'removeDonateButton' to true
|
|
|
|
|
* You can disable any solicitations for donations by setting 'removeDonateButton' to true,
|
|
|
|
|
* but we'd appreciate it if you didn't!
|
|
|
|
|
*/
|
|
|
|
|
allowSubscriptions: true,
|
|
|
|
|
removeDonateButton: false,
|
|
|
|
|
//removeDonateButton: false,
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* By default, CryptPad also contacts our accounts server once a day to check for changes in
|
|
|
|
|
* the people who have accounts. This check-in will also send the version of your CryptPad
|
|
|
|
|
* instance and your email so we can reach you if we are aware of a serious problem. We will
|
|
|
|
|
* never sell it or send you marketing mail. If you want to block this check-in and remain
|
|
|
|
|
* completely invisible, set this and allowSubscriptions both to false.
|
|
|
|
|
/* CryptPad will display a point of contact for your instance on its contact page
|
|
|
|
|
* (/contact.html) if you provide it below.
|
|
|
|
|
*/
|
|
|
|
|
adminEmail: 'i.did.not.read.my.config@cryptpad.fr',
|
|
|
|
|
|
|
|
|
|
/* Sales coming from your server will be identified by your domain
|
|
|
|
|
*
|
|
|
|
|
* If you are using CryptPad in a business context, please consider taking a support contract
|
|
|
|
|
* by contacting sales@cryptpad.fr
|
|
|
|
|
*/
|
|
|
|
|
myDomain: _domain,
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* If you are using CryptPad internally and you want to increase the per-user storage limit,
|
|
|
|
|
* change the following value.
|
|
|
|
|
* By default, CryptPad contacts one of our servers once a day.
|
|
|
|
|
* This check-in will also send some very basic information about your instance including its
|
|
|
|
|
* version and the adminEmail so we can reach you if we are aware of a serious problem.
|
|
|
|
|
* We will never sell it or send you marketing mail.
|
|
|
|
|
*
|
|
|
|
|
* Please note: This limit is what makes people subscribe and what pays for CryptPad
|
|
|
|
|
* development. Running a public instance that provides a "better deal" than cryptpad.fr
|
|
|
|
|
* is effectively using the project against itself.
|
|
|
|
|
* If you want to block this check-in and remain set 'blockDailyCheck' to true.
|
|
|
|
|
*/
|
|
|
|
|
defaultStorageLimit: 50 * 1024 * 1024,
|
|
|
|
|
//blockDailyCheck: false,
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* CryptPad allows administrators to give custom limits to their friends.
|
|
|
|
|
* add an entry for each friend, identified by their user id,
|
|
|
|
|
* which can be found on the settings page. Include a 'limit' (number of bytes),
|
|
|
|
|
* a 'plan' (string), and a 'note' (string).
|
|
|
|
|
* By default users get 50MB of storage by registering on an instance.
|
|
|
|
|
* You can set this value to whatever you want.
|
|
|
|
|
*
|
|
|
|
|
* hint: 1GB is 1024 * 1024 * 1024 bytes
|
|
|
|
|
*/
|
|
|
|
|
customLimits: {
|
|
|
|
|
/*
|
|
|
|
|
"https://my.awesome.website/user/#/1/cryptpad-user1/YZgXQxKR0Rcb6r6CmxHPdAGLVludrAF2lEnkbx1vVOo=": {
|
|
|
|
|
limit: 20 * 1024 * 1024 * 1024,
|
|
|
|
|
plan: 'insider',
|
|
|
|
|
note: 'storage space donated by my.awesome.website'
|
|
|
|
|
},
|
|
|
|
|
"https://my.awesome.website/user/#/1/cryptpad-user2/GdflkgdlkjeworijfkldfsdflkjeEAsdlEnkbx1vVOo=": {
|
|
|
|
|
limit: 10 * 1024 * 1024 * 1024,
|
|
|
|
|
plan: 'insider',
|
|
|
|
|
note: 'storage space donated by my.awesome.website'
|
|
|
|
|
}
|
|
|
|
|
* hint: 50MB is 50 * 1024 * 1024
|
|
|
|
|
*/
|
|
|
|
|
},
|
|
|
|
|
//defaultStorageLimit: 50 * 1024 * 1024,
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/* =====================
|
|
|
|
|
* STORAGE
|
|
|
|
|
* ===================== */
|
|
|
|
|
|
|
|
|
|
/* By default the CryptPad server will run scheduled tasks every five minutes
|
|
|
|
|
* If you want to run scheduled tasks in a separate process (like a crontab)
|
|
|
|
|
* you can disable this behaviour by setting the following value to true
|
|
|
|
|
*/
|
|
|
|
|
disableIntegratedTasks: false,
|
|
|
|
|
|
|
|
|
|
/* Pads that are not 'pinned' by any registered user can be set to expire
|
|
|
|
|
* after a configurable number of days of inactivity (default 90 days).
|
|
|
|
|
* The value can be changed or set to false to remove expiration.
|
|
|
|
|
* Expired pads can then be removed using a cron job calling the
|
|
|
|
|
* `delete-inactive.js` script with node
|
|
|
|
|
* `evict-inactive.js` script with node
|
|
|
|
|
*
|
|
|
|
|
* defaults to 90 days if nothing is provided
|
|
|
|
|
*/
|
|
|
|
|
inactiveTime: 90, // days
|
|
|
|
|
//inactiveTime: 90, // days
|
|
|
|
|
|
|
|
|
|
/* CryptPad archives some data instead of deleting it outright.
|
|
|
|
|
* This archived data still takes up space and so you'll probably still want to
|
|
|
|
@ -241,31 +180,46 @@ module.exports = {
|
|
|
|
|
* deletion. Set this value to the number of days you'd like to retain
|
|
|
|
|
* archived data before it's removed permanently.
|
|
|
|
|
*
|
|
|
|
|
* defaults to 15 days if nothing is provided
|
|
|
|
|
*/
|
|
|
|
|
archiveRetentionTime: 15,
|
|
|
|
|
//archiveRetentionTime: 15,
|
|
|
|
|
|
|
|
|
|
/* Max Upload Size (bytes)
|
|
|
|
|
* this sets the maximum size of any one file uploaded to the server.
|
|
|
|
|
* anything larger than this size will be rejected
|
|
|
|
|
* defaults to 20MB if no value is provided
|
|
|
|
|
*/
|
|
|
|
|
maxUploadSize: 20 * 1024 * 1024,
|
|
|
|
|
//maxUploadSize: 20 * 1024 * 1024,
|
|
|
|
|
|
|
|
|
|
// XXX
|
|
|
|
|
premiumUploadSize: 100 * 1024 * 1024,
|
|
|
|
|
|
|
|
|
|
/* =====================
|
|
|
|
|
* HARDWARE RELATED
|
|
|
|
|
* ===================== */
|
|
|
|
|
|
|
|
|
|
/* CryptPad's file storage adaptor closes unused files after a configurable
|
|
|
|
|
* number of milliseconds (default 30000 (30 seconds))
|
|
|
|
|
/*
|
|
|
|
|
* CryptPad allows administrators to give custom limits to their friends.
|
|
|
|
|
* add an entry for each friend, identified by their user id,
|
|
|
|
|
* which can be found on the settings page. Include a 'limit' (number of bytes),
|
|
|
|
|
* a 'plan' (string), and a 'note' (string).
|
|
|
|
|
*
|
|
|
|
|
* hint: 1GB is 1024 * 1024 * 1024 bytes
|
|
|
|
|
*/
|
|
|
|
|
channelExpirationMs: 30000,
|
|
|
|
|
/*
|
|
|
|
|
customLimits: {
|
|
|
|
|
"https://my.awesome.website/user/#/1/cryptpad-user1/YZgXQxKR0Rcb6r6CmxHPdAGLVludrAF2lEnkbx1vVOo=": {
|
|
|
|
|
limit: 20 * 1024 * 1024 * 1024,
|
|
|
|
|
plan: 'insider',
|
|
|
|
|
note: 'storage space donated by my.awesome.website'
|
|
|
|
|
},
|
|
|
|
|
"https://my.awesome.website/user/#/1/cryptpad-user2/GdflkgdlkjeworijfkldfsdflkjeEAsdlEnkbx1vVOo=": {
|
|
|
|
|
limit: 10 * 1024 * 1024 * 1024,
|
|
|
|
|
plan: 'insider',
|
|
|
|
|
note: 'storage space donated by my.awesome.website'
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* CryptPad's file storage adaptor is limited by the number of open files.
|
|
|
|
|
* When the adaptor reaches openFileLimit, it will clean up older files
|
|
|
|
|
/* Users with premium accounts (those with a plan included in their customLimit)
|
|
|
|
|
* can benefit from an increased upload size limit. By default they are restricted to the same
|
|
|
|
|
* upload size as any other registered user.
|
|
|
|
|
*
|
|
|
|
|
*/
|
|
|
|
|
openFileLimit: 2048,
|
|
|
|
|
//premiumUploadSize: 100 * 1024 * 1024,
|
|
|
|
|
|
|
|
|
|
/* =====================
|
|
|
|
|
* DATABASE VOLUMES
|
|
|
|
|