Infra
/
lemur
5
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request #177 from kevgliss/docs 

clarifying upgrade process
This commit is contained in:
kevgliss 2015-12-09 17:29:13 -08:00
parent 1e67329c64 4db7931aa0
commit 9b927cfcc2
2 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/administration/index.rst
View File

@ -493,6 +493,11 @@ version of Lemur from pypi and then apply any schema changes with the following
.. note:: Internally, this uses `Alembic <https://alembic.readthedocs.org/en/latest/>`_ to manage database migrations.
.. note:: By default Alembic looks for the `migrations` folder in the current working directory.
The migrations folder is located under `<LEMUR_HOME>/lemur/migrations` if you are running the lemur command from any
location besides `<LEMUR_HOME>/lemur` you will need to pass the `-d` flag to specify the absolute file path to the
`migrations` folder.
.. _CommandLineInterface:
Command Line Interface

1
docs/quickstart/index.rst
View File

@ -158,7 +158,6 @@ Additional notifications can be created through the UI or API. See :ref:`Creati
.. code-block:: bash
$ lemur db init
$ lemur init
.. note:: It is recommended that once the ``lemur`` user is created that you create individual users for every day access. There is currently no way for a user to self enroll for Lemur access, they must have an administrator create an account for them or be enrolled automatically through SSO. This can be done through the CLI or UI. See :ref:`Creating Users <CreatingUsers>` and :ref:`Command Line Interface <CommandLineInterface>` for details.