Merge branch 'master' into docker-docs
This commit is contained in:
@ -151,6 +151,15 @@ Specifying the `SQLALCHEMY_MAX_OVERFLOW` to 0 will enforce limit to not create c
|
||||
to start. Multiple keys can be provided to facilitate key rotation. The first key in the list is used for
|
||||
encryption and all keys are tried for decryption until one works. Each key must be 32 URL safe base-64 encoded bytes.
|
||||
|
||||
Only fields of type ``Vault`` will be encrypted. At present, only the following fields are encrypted:
|
||||
|
||||
* ``certificates.private_key``
|
||||
* ``pending_certificates.private_key``
|
||||
* ``dns_providers.credentials``
|
||||
* ``roles.password``
|
||||
|
||||
For implementation details, see ``Vault`` in ``utils.py``.
|
||||
|
||||
Running lemur create_config will securely generate a key for your configuration file.
|
||||
If you would like to generate your own, we recommend the following method:
|
||||
|
||||
|
@ -130,7 +130,7 @@ Once created, you will need to update the configuration file with information ab
|
||||
vi ~/.lemur/lemur.conf.py
|
||||
|
||||
.. note:: If you are unfamiliar with the SQLALCHEMY_DATABASE_URI string it can be broken up like so:
|
||||
``postgresql://userame:password@<database-fqdn>:<database-port>/<database-name>``
|
||||
``postgresql://username:password@<database-fqdn>:<database-port>/<database-name>``
|
||||
|
||||
Before Lemur will run you need to fill in a few required variables in the configuration file:
|
||||
|
||||
|
Reference in New Issue
Block a user