Version 4.0.0

Improved

• Use Ruby 3.0.
• Upgraded baseimage-docker to rel-2.1.0.
• It is now possible to define the user name as well as UID and GID of the
  main user running the container. By default, this will be user dora with
  UID 1000 and GID 1000.
• It is now possible to bootstrap a new Rails application, plugin or whatever
  because the script that bootstraps the container no longer errors out if there
  is no Rails application present. Instead, when configured not to pull any Git
  repository (GIT_PULL=false), the script will gracefully exit if there is
  no Rails application.
• The WEBHOOK_SECRET environment variable was renamed to
  DORA_WEB_UPGRADER_SECRET to play nice with DoraWebUpgrader.

Changed

• The default name for the Git branch to checkout was changed from master to
  main. On the other hand, e-mail addresses such as webmaster@... were not
  changed. However, in the author's opinion, where is a difference between
  "master" and "slave" terminology on the one hand and "master" as in
  "someone is professionally trained to do something really well" on the other
  (in Germany, "Meister" is a professional title).
• The msmtp configuration now uses TLS, rather than STARTSSL, to communicate
  with the SMTP server.

Fixed

• Adjust runit's service permissions for sidekiq so that it can be stopped and
  restarted by the 'dora' group.
• The shared-mime-info package is now explicitly installed (following recent
  licensing changes in the wider Rails ecosystem).
• Prevent flooding the container output with warnings if there is no log
  directory.
• When upgrading the application, upgrade-app.sh will now stop and re-start
  the sidekiq service.
• Properly add the restart-app.sh script rather than another copy of the
  upgrade-app.sh script into the image.

Version 3.0.1

Fixed

• Fixed a fatal typo in the bootstrapping script.
• Exit gracefully during msmtp configuration to not make the bootstrapping fail.
• Do not use uptime in the status reports as it would reflect the host's
  uptime rather than the container uptime.

Version 3.0.0

Breaking change

• The app user and group were renamed from 'app' (passenger-docker's default)
  to 'dora' in order to further eliminate confusion. Now there is only one
  directory named 'app', and that is the said directory in a Rails application.
  Important: If you relay e-mails into your dora container as described in
  README.md, you will need to adjust the paths in your mail server configuration
  files, e.g. master.cf if you use Postfix.

New

• Implemented basic status reporting.

Fixed

• rails-console.sh now invokes rails as the app user.
• Removed the erroneous server_name directive from the Nginx site configuration
  file.

Version 2.1.0

Version 2.1.0 (2020-09-15)

Improved

• Added a simple locking mechanism to the upgrade-app.sh script. When Git web
  hooks are invoked after a push to the repository, the upgrade script may be
  called twice in quick succession, once for the commits push and once for the
  tags push.

Fixed

• Use passenger-ruby27 rather than passenger-ruby26 as base image.
• Copy the right rails-console.sh helper script into the image.
• Fix setting the PATH variable to include the path to the bin directory.
• The rails command in the rails-console.sh helper script was missing the
  actual command.
• The nodejs installation script now respects the container's operating
  system's code name.

Changed

• Various rather cosmetic improvements to script output.

Version 1.2.0

- Configure the container's time zone using the `$TIMEZONE` environment
  variable.