I’ve added a 10 tag to zulip-postgresql, current pointing to the same
image as latest. Since upgrading to a new major version requires a
manual migration, we shouldn’t encourage it to happen automatically.
Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
This release is being done because 2.0.4-0 was incorrectly build off
the wrong commit in zulip/zulip (due to a mispushed tag), and has
about 1000 commits of development from master in it.
Pushing this will fix the situation for folks who are doing new
installations; we recommend folks running 2.0.4-0 not upgrade.
Fixes#201.
Currently this conditional results in `exit 1` when the backups
directory does exist. This change flips the logic to complain
when there are no backup files which, based on the error message,
is the intended result.
The previous code wrote
MAILTO=\n30 3 * * * cd /;/entrypoint.sh app:backup
(with a literal backslash n).
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
To match zulip/puppet/zulip/files/limits.conf,
zulip/puppet/zulip/files/supervisor/supervisord.conf. Otherwise we
inherit the Docker daemon’s limits, which are too small when Docker is
installed as a snap.
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
Apparently, it's kinda a pain to modify the passwords for
rabbitmq/postgres, so document that fact.
A nice v2 would be to link to docs for exactly how to rotate these
passwords.
This took me 30min ... "SETTINGS_EXTERNAL_HOST" is wrong, and will lead to problems. The correct one used in entrypoint.sh is "SETTING_EXTERNAL_HOST" with no 'S', same goes for other settings.
This fixes a bug introduced in
62bf74190b, where the template
settings.py content wasn't being put in place properly.
The previous model meant that if the user exported the settings.py
file to the data directory, we'd end up appending various versions of
the users' configuration to it over time.
While those users should have been using the MANUAL_CONFIGURATION
setting, this at least is a much cleaner model for managing configuration.
Fixes#130.
Fixes#153.
Fixes#155.
Since these files are intended to be automatically generated by
entrypoint.sh at container startup time, these files are at best
useless and at worst could result in users ending up with copies of
the secrets generated when the Docker image they were using was built.
The ignore option was removed a long time ago, and the settings style
variable for RabbitMQ is very old backwards-compatibility code that is
no longer needed.
Single quotes in YAML have fewer situations where escaping is relevant
than double-quotes, which means using them as the default will help
prevent users from running into escaping issues.
Using an actual tool designed to do this is a lot more robust and
fixes some nasty escaping issues involving secrets containing `~` that
were reported in #143.
