diff options
author | Mike Bayer <mike_mp@zzzcomputing.com> | 2019-11-15 19:13:11 -0500 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2019-11-15 19:15:39 -0500 |
commit | 98bb57133bae6cc5ebd72fbc09cd5ccd056bdf0b (patch) | |
tree | 89c435209d6dda0260eaa681a4642fc2fc0799ac /docs/build/front.rst | |
parent | bf462e637ed38bf19e0dbf2b6a007fa2468fcfef (diff) | |
download | alembic-98bb57133bae6cc5ebd72fbc09cd5ccd056bdf0b.tar.gz |
Restate installation and tutorial in terms of a virtualenv
Since we have things like "cd myproject" in the documentation,
we are assuming some knowledge of how the project is set up.
As the vast majority of projects will have import statements
in their env.py, restate this documentation in terms of a
virtual environment where the local project is installed
in editable mode.
Change-Id: I6a11c5077c02a00145cb882b43d6c9a7c986e375
Fixes: #625
Diffstat (limited to 'docs/build/front.rst')
-rw-r--r-- | docs/build/front.rst | 45 |
1 files changed, 39 insertions, 6 deletions
diff --git a/docs/build/front.rst b/docs/build/front.rst index d288472..ebafa1f 100644 --- a/docs/build/front.rst +++ b/docs/build/front.rst @@ -19,16 +19,49 @@ The most recent published version of this documentation should be at https://ale Installation ============ -Install released versions of Alembic from the Python package index with `pip <http://pypi.python.org/pypi/pip>`_ or a similar tool:: +Installation of Alembic is typically local to a project setup and it is usually +assumed that an approach like `virtual environments +<https://docs.python.org/3/tutorial/venv.html>`_ are used, which would include +that the target project also `has a setup.py script +<https://packaging.python.org/tutorials/packaging-projects/>`_. - pip install alembic +The documentation below is **only one kind of approach to installing Alembic for a +project**; there are many such approaches. The documentation below is +provided only for those users who otherwise have no specific project setup +chosen. -Installation via source distribution is via the ``setup.py`` script:: +To build a virtual environment for a specific project, first we assume that +`Python virtualenv <https://pypi.org/project/virtualenv/>`_ is installed +systemwide. Then:: - python setup.py install + $ cd /path/to/your/project + $ virtualenv .venv -The install will add the ``alembic`` command to the environment. All operations with Alembic -then proceed through the usage of this command. +There is now a Python interpreter that you can access in +``/path/to/your/project/.venv/bin/python``, as well as the `pip +<http://pypi.python.org/pypi/pip>`_ installer tool in +``/path/to/your/project/.venv/bin/pip``. + +We now install Alembic as follows:: + + $ /path/to/your/project/.venv/bin/pip install alembic + +The install will add the ``alembic`` command to the virtual environment. All +operations with Alembic in terms of this specific virtual environment will then +proceed through the usage of this command, as in:: + + $ /path/to/your/project/.venv/bin/alembic init . + +Next, we ensure that the local project is also installed, in a development environment +this would be in `editable mode <https://pip.pypa.io/en/stable/reference/pip_install/#editable-installs>`_:: + + $ /path/to/your/project/.venv/bin/pip install -e . + +As a final step, the `virtualenv activate <https://virtualenv.pypa.io/en/latest/userguide/#activate-script>`_ +tool can be used so that the ``alembic`` command is available without any +path information, within the context of the current shell:: + + $ source /path/to/your/project/.venv/bin/activate Dependencies ------------ |