upgrading from packages does not require manual intervention
And since the PyPI are no longer updated, there is no need to update the manual installation instructions. License: MIT
This commit is contained in:
parent
74bac945ba
commit
ac10c7ac1a
|
@ -25,7 +25,6 @@ Quickstart guides and installation guidelines
|
|||
|
||||
|
||||
change_db
|
||||
upgrading
|
||||
deployment
|
||||
|
||||
Quickstarts
|
||||
|
|
|
@ -1,17 +0,0 @@
|
|||
.. _upgrading:
|
||||
|
||||
=========
|
||||
Upgrading
|
||||
=========
|
||||
|
||||
Update using pip::
|
||||
|
||||
pip install -U authentic2
|
||||
|
||||
Authentic store all its data in a relational database as specified in its
|
||||
settings.py or local_settings.py file. So in order to upgrade to a new version
|
||||
of authentic you have to update your database schema using the
|
||||
migration command — you will need to have installed the dependency django-south,
|
||||
see the beginning of this README file.::
|
||||
|
||||
authentic2-ctl syncdb --migrate
|
Reference in New Issue