defaults/main.yml

@@ -8,7 +8,7 @@ cryptpad_pkg:
 cryptpad_node_version: '12'
 
 cryptpad_path: '/var/www/cryptpad'
-cryptpad_version: "4.3.1"
+cryptpad_version: "4.4.0"
 
 cryptpad_httpUnsafeOrigin: "http://localhost:3000"
 cryptpad_httpSafeOrigin: ''
@@ -34,6 +34,7 @@ cryptpad_taskPath: "./data/tasks"
 cryptpad_blockPath: "./block"
 cryptpad_blobPath: "./blob"
 cryptpad_blobStagingPath: "./data/blobstage"
+cryptpad_decreePath: "./data/decrees"
 cryptpad_logPath: "./data/logs"
 cryptpad_logToStdout: "false"
 cryptpad_logLevel: "info"
@@ -61,3 +62,4 @@ nginx_vhosts:
   letsencrypt: 'false'
   ssl_name: 'cryptpad.server.org'
   proxy_pass: 'localhost'
+  debug: 'false'

templates/config/config.js.j2

@@ -45,6 +45,14 @@ module.exports = {
  *  In such a case this should be also handled by NGINX, as documented in
  *  cryptpad/docs/example.nginx.conf (see the $main_domain variable)
  *
+ *  Note: you may provide multiple origins for the purpose of accessing
+ *  a development instance via different URLs, like so:
+ *  httpUnsafeOrigin: 'http://127.0.0.1:3000/ http://localhost:3000/',
+ *
+ *  Such configuration is not recommended for production instances,
+ *  as the development team does not actively test such configuration
+ *  and it may have unintended consequences in practice.
+ *
  */
     httpUnsafeOrigin: '{{ cryptpad_httpUnsafeOrigin }}',
 
@@ -294,6 +302,8 @@ module.exports = {
      */
     blobStagingPath: '{{ cryptpad_blobStagingPath }}',
 
+    decreePath: '{{ cryptpad_decreePath }}',
+
     /* CryptPad supports logging events directly to the disk in a 'logs' directory
      * Set its location here, or set it to false (or nothing) if you'd rather not log
      */