blob: 4bdc656c801003306a6ac3c617143bc1d67a0f19 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
Upgrading
=========
Fietsboek does not currently have an automated updater, however it is quite
simple to update Fietsboek manually.
.. warning::
Make sure to have backups of your user data ready in case the upgrade fails!
.. note::
It is advised to stop the Fietsboek server during the backup process.
Pulling the New Code
--------------------
First, we need to pull the new code. This step depends on the source that you
have installed Fietsboek from. In the case that you use ``git``, this can be
done in the following way:
.. code:: bash
git pull
git checkout v42.0 # Put in the version that you want to update to here
If you have downloaded an archive with the Fietsboek source, you need to
download the archive with the new version and extract it somewhere.
Installing the Python Module
----------------------------
Use ``pip`` to install the new version of the Fietsboek package, as well as any
new additional dependencies:
.. code:: bash
.venv/bin/pip install .
This step is similar to the command that you used when installing Fietsboek
initially.
Note that removed dependencies are not automatically removed. It might be worth
to start with a clean virtual environment from time to time to clear out old
cruft.
Upgrading the Database
----------------------
.. warning::
It cannot be stressed enough that you should have backups of your data. This
is your last chance.
Some updates might change the database schema. Those updates come with database
migrations that can adapt an existing database to the new schema. In order to
do so, use ``alembic``:
.. code:: bash
.venv/bin/alembic -c production.ini upgrade head
Restarting Fietsboek
--------------------
You can now run Fietsboek again. This step depends on the method that you use
to deploy Fietsboek.
|
