From 4db7931aa0d3e4dc1fc918f36bb11862ab908549 Mon Sep 17 00:00:00 2001 From: kevgliss Date: Wed, 9 Dec 2015 17:18:01 -0800 Subject: [PATCH] clarifying upgrade process --- docs/administration/index.rst | 5 +++++ docs/quickstart/index.rst | 1 - 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/administration/index.rst b/docs/administration/index.rst index 7bc80b98..f9cf293b 100644 --- a/docs/administration/index.rst +++ b/docs/administration/index.rst @@ -493,6 +493,11 @@ version of Lemur from pypi and then apply any schema changes with the following .. note:: Internally, this uses `Alembic `_ 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/migrations` if you are running the lemur command from any +location besides `/lemur` you will need to pass the `-d` flag to specify the absolute file path to the +`migrations` folder. + .. _CommandLineInterface: Command Line Interface diff --git a/docs/quickstart/index.rst b/docs/quickstart/index.rst index 621b163e..60d82ea1 100644 --- a/docs/quickstart/index.rst +++ b/docs/quickstart/index.rst @@ -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 ` and :ref:`Command Line Interface ` for details.