2019-03-07 15:35:54 +00:00
|
|
|
.. include:: /_includes/snippets/__ANNOUNCEMENTS__.rst
|
|
|
|
|
|
2018-07-03 13:47:58 +00:00
|
|
|
.. _checkout-different-devilbox-release:
|
|
|
|
|
|
|
|
|
|
***********************************
|
|
|
|
|
Checkout different Devilbox release
|
|
|
|
|
***********************************
|
|
|
|
|
|
|
|
|
|
You now have the devilbox downloaded at the latest version (``git master branch``). This is also recommended as it receives
|
|
|
|
|
bugfixes frequently. If you however want to stay on a stable release, you need to check out a
|
|
|
|
|
specific ``git tag``.
|
|
|
|
|
|
|
|
|
|
Lets say you want your devilbox setup to be at release ``0.12.1``, all you have to do is to check out
|
|
|
|
|
this specific git tag.
|
|
|
|
|
|
|
|
|
|
.. code-block:: bash
|
|
|
|
|
|
|
|
|
|
host> cd path/to/devilbox
|
|
|
|
|
host> git checkout 0.12.1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.. warning::
|
|
|
|
|
Whenever you check out a different version, make sure that your ``.env`` file is up-to-date
|
|
|
|
|
with the bundled ``env-example`` file. Different Devilbox releases might require different
|
|
|
|
|
settings to be available inside the ``.env`` file. Refer to the next section for how to
|
|
|
|
|
create the ``.env`` file.
|
|
|
|
|
|
|
|
|
|
|
