You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* :ref:`Central v2023.3 <central-upgrade-2023.3>`: clean up old database if needed
@@ -91,6 +92,33 @@ You'll be asked to confirm the removal of all dangling images. Agree by typing t
91
92
Version-specific upgrade instructions
92
93
--------------------------------------
93
94
95
+
.. _central-upgrade-2024.2:
96
+
97
+
Upgrading to Central v2024.2
98
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
99
+
100
+
There are no required special steps related to this upgrade. However, there are some optional changes that you may want to know about or opt into.
101
+
102
+
1. Configuration no longer requires rebuilding
103
+
**********************************************
104
+
105
+
If you make changes to your `.env` file to configure Central as described in the :doc:`setup instructions <central-install-digital-ocean>`, you no longer have to rebuild Central for the changes to take effect. Instead, a stop and restart is now enough:
106
+
107
+
.. code-block:: bash
108
+
109
+
$ docker compose stop
110
+
$ docker compose up -d
111
+
112
+
2. File data can be stored in S3-compatible storage
By default, Central stores all of its data in a database, including files like images attached to submissions. If you have or plan on collecting a lot of files, you may prefer to store these in separate storage to reduce load on the database and possibly reduce hosting costs. See instructions on how to opt in.
116
+
117
+
3. Docker images now published
118
+
*******************************
119
+
120
+
If you use your own infrastructure for orchestrating the different components needed to run Central, you may prefer to use published Docker images. You can now find these `on GHCR <https://github.com/orgs/getodk/packages?tab=packages&repo_name=central>`_.
0 commit comments