ODK Central v1.5

Releases
4

ODK Central v1.5.3 is now available and includes several changes. Please take special note if you use encrypted backups to Google Drive or if you have disabled or customized Sentry.

As previously announced here, on January 31st, 2023, encrypted backups to Google Drive will stop working. Central v1.5.3 removes the ability to set up backups to Google Drive. If you already have backups set up, your backups will continue working until January 31st, 2023. A warning will be shown on the Backups page.

By default, Central uses Sentry for error logging, which provides the ODK core team with an anonymized log of unexpected programming errors that occur while the server is running. If you have disabled or customized Sentry, then when you upgrade to Central v1.5.3, you will need to follow special instructions. That's because we've updated Central's Sentry configuration to match a planned change to the Sentry API. If you have not changed how Sentry is configured, you do not need to follow these special upgrade instructions.

If you have disabled Sentry

Since you have modified files/service/config.json.template, you will see an error message when you run the git pull command:

error: Your local changes to the following files would be overwritten by merge:
        files/service/config.json.template
Please commit your changes or stash them before you merge.

Don't worry, nothing bad happens if you see this. To get around this error, run this set of commands instead of git pull:

mv files/service/config.json.template config-tmp
git pull
mv config-tmp files/service/config.json.template

After following these steps, you can continue with the regular upgrade instructions.

If you have customized Sentry

Since you have modified files/service/config.json.template, you will see an error message when you run the git pull command:

error: Your local changes to the following files would be overwritten by merge:
        files/service/config.json.template
Please commit your changes or stash them before you merge.

Don't worry, nothing bad happens if you see this. To get around this error, run this set of commands instead of git pull:

mv files/service/config.json.template config-tmp
git pull
mv config-tmp files/service/config.json.template

Next, modify files/service/config.json.template. Below the line that contains "sentry": {, insert a new line that looks like this:

"orgSubdomain": "SENTRY_ORGANIZATION_SUBDOMAIN",

Replace SENTRY_ORGANIZATION_SUBDOMAIN with your Sentry organization subdomain.

After following these steps, you can continue with the regular upgrade instructions.

Central v1.5.3 takes steps to fix database connection leaks, which could cause Central to become unresponsive. Central will now automatically clean up database streams that have become inactive. Thank you to @jcwatson11 and @abhishek for reporting this issue and to everyone who has contributed to the discussion around this issue.

Central v1.5.3 also includes the following changes:

  • Handle errors when creating a database stream.
  • Set security headers at the root path.
  • Don’t include referrer information in cross-origin requests.
  • Update Enketo.
  • Update the server url configuration for Enketo.
  • Update translations.
10 Likes