/usr/share/bibledit/config/config.txt is in bibledit-data 5.0.453-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 | Bibledit Cloud Configuration
All configuration files reside in the config folder.
When Bibledit Cloud runs behind a proxy server, Bibledit is not able to find out its own URL that faces the user.
The user-facing URL can be set through a configuration file.
The name of the configuration file is:
userfacingurl.conf
It contains the URL, for example:
https://bibledit.org:1500/
An example configuration file is included: userfacingurl.txt
The secure http server needs a private key and a public certificate.
Bibledit Cloud comes with a key and a certificate that work for localhost.daplie.com, which resolves to localhost.
They are taken from https://github.com/Daplie/localhost.daplie.com-certificates.
In case Bibledit Cloud runs on a public server and uses secure http, it will read the private key and the public certificate and the chain of trusted certificate authorities from the following three files:
* server.key: The private key for the server.
* server.crt: The public certificate for the server.
* authorities.crt: The chain of trusted certificate authorities that have issued the server certificate. At the top of the file will be the intermediate authority that issued the server certificate. Next can be more intermediate authorities. At the bottom of the file should be the trusted root certificate.
Three example files are included. All of them have the "local." prefix. Bibledit will use them in case the proper files are not there.
Secure certificates can be purchased from many authorities.
Free certificates are available from https://letsencrypt.org/ and https://www.startssl.com/ and more.
Here is an example of how to get and update certificates through Let's Encrypt:
1. Obtain the certificate: $ letsencrypt-auto certonly --webroot -w /var/www/bibledit.org -d bibledit.org -d www.bibledit.org
2. Regularly renew it: $ letsencrypt-auto renew
3. Copy the renewed certificates into place:
$ cp /etc/letsencrypt/live/bibledit.org/privkey.pem /home/foo/bibledit/config/server.key
$ cp /etc/letsencrypt/live/bibledit.org/cert.pem /home/foo/bibledit/config/server.crt
$ cp /etc/letsencrypt/live/bibledit.org/chain.pem /home/foo/bibledit/config/authorities.crt
After the certificates have been updated, Bibledit Cloud needs to be restarted, and it will then load the new certificates.
To enforce secure http for browser communications, put a file named browser.https in the config folder.
The file may be empty. Once this file is found, Bibledit Cloud will redirect any incoming http browser traffic to https traffic.
A file with the name of client.https will do the same for Bibledit client traffic.
OpenLDAP server: See file ldap.txt for more information.
Network port for http server: The default value is 8080. Put a different port number in file "network-port".
Administrator details: To preset the administrator's account, put the details in the files "admin-username" and "admin-password" and "admin-email", one detail per file.
Demo installation: If the file config/demo is present, it behaves as a demo installation.
Obfuscating the user interface: See folder obfuscate for more information.
|