CryptPad _should_ work with an unmodified configuration file, though there are many things which you may want to customize.
Attributes in the config should have comments indicating how they are used.
```
$EDITOR config.js
```
If you are deploying CryptPad in a production environment, we recommend that you take the time to understand and correctly customize your server's [Content Security Policy headers](https://content-security-policy.com/).
Modern browsers use these headers to allow or deny actions from malicious clients which could compromise the confidentiality of your user's data.
These settings can be found in your configuration file in the `contentSecurity` and `padContentSecurity` sections.
## Maintenance
Before upgrading your CryptPad instance to the latest version, we recommend that you check what has changed since your last update.
You can do so by checking which version you have (see package.json), and comparing it against newer [release notes](https://github.com/xwiki-labs/cryptpad/releases).
To get access to the most recent codebase:
```
cd /your/cryptpad/instance/location;
git pull
```
To update dependencies:
```
# clientside dependencies
bower update;
# serverside dependencies
It also contains information on keeping your instance of CryptPad up to date.
npm update;
```
## Deleting all data and resetting Cryptpad
## Setup using Docker
To reset your instance of Cryptpad and remove all the data that is being stored:
See [Cryptpad-Docker](docs/cryptpad-docker.md)
**WARNING: This will reset your Cryptpad instance and remove all data**
```
# change into your cryptpad directory
cd /your/cryptpad/instance/location;
# delete the datastore
rm -rf ./datastore
```
If you are using the mongodb adaptor, [drop the relevant collection](https://docs.mongodb.org/manual/reference/method/db.collection.drop/#db.collection.drop).
If you are using the [leveldb adaptor](https://github.com/xwiki-labs/cryptpad-level-store), delete the datastore directory you have configured.
## Testing
To test CryptPad, go to http://your.server:3000/assert/
You can use WebDriver to run this test automatically by running TestSelenium.js but you will need chromedriver installed.
If you use Mac, you can `brew install chromedriver`.
## Developing CryptPad
CryptPad is built with a lot of small javascript libraries.
To make js files load faster, we apply an aggressive caching policy.
If you want to add new features to CryptPad, you'll want to turn off caching.
You can do so by launching your server in _dev mode_, like so:
`DEV=1 node server.js`
## Security
# Security
CryptPad is *private*, not *anonymous*. Privacy protects your data, anonymity protects you.
CryptPad is *private*, not *anonymous*. Privacy protects your data, anonymity protects you.
As such, it is possible for a collaborator on the pad to include some silly/ugly/nasty things
As such, it is possible for a collaborator on the pad to include some silly/ugly/nasty things
@ -127,11 +41,7 @@ the battery out of your computer before it spawns Agent Smith.
Still there are other low-lives in the world so using CryptPad over HTTPS is probably a good idea.
Still there are other low-lives in the world so using CryptPad over HTTPS is probably a good idea.
## Setup using Docker
# Translations
See [Cryptpad-Docker](docs/cryptpad-docker.md)
## Translations
We'd like to make it easy for more people to use encryption in their routine activities.
We'd like to make it easy for more people to use encryption in their routine activities.
As such, we've tried to make language-specific parts of CryptPad translatable. If you're
As such, we've tried to make language-specific parts of CryptPad translatable. If you're
@ -139,14 +49,14 @@ able to translate CryptPad's interface, and would like to help, please contact u
You can also see [our translation guide](/customize.dist/translations/README.md).
You can also see [our translation guide](/customize.dist/translations/README.md).
## Contacting Us
# Contacting Us
You can reach members of the CryptPad development team on [twitter](https://twitter.com/cryptpad),
You can reach members of the CryptPad development team on [Twitter](https://twitter.com/cryptpad),
via our [github issue tracker](https://github.com/xwiki-labs/cryptpad/issues/), on the
via our [GitHub issue tracker](https://github.com/xwiki-labs/cryptpad/issues/), on our
ansuz
7 years ago
