2.0.0

Here's release 2.0.0 with:

• A new name 😄; we're now Consul Democracy!
• Multitenancy, which allows managing multiple institutions using just one Consul Democracy installation
• An option to allow multiple answers per question in a poll
• Polygon areas in geozones that can be displayed on a budget's map
• A full translation to the Nepali language
• Maintenance updates like upgrading to Rails 6.0 and Ruby 3.0
• Automatic monitoring of Delayed Job processes
• Many bug fixes and small improvements

Check the Changelog to see all the changes. Please take your time reading all referenced pull requests to understand new features and changes.

This release is dedicated to the memory of Pablo García (@pablovg2). We'll always be thankful for his contributions to this project and we send our deepest condolences and best wishes to his family and his coworkers at @enredacoop.

Updating your fork

Check how to keep your fork updated; if you're updating from release 1.5.0, you can just:

git checkout master
git pull
git checkout -b release
git fetch upstream tag 2.0.0
git merge 2.0.0
git checkout master
git merge release
git branch -d release
git push

⚙️ After deploying the new version, execute the release tasks:

bin/rake consul:execute_release_tasks RAILS_ENV=production

Thanks to a collaboration with the Cabildo de Tenerife, we've added support for multitenancy, that is, managing different institutions using just one Consul Democracy installation. Although we've done several tests in order to experience a smooth upgrade from previous version of Consul Democracy so this feature doesn't affect existing installations, as usual we still recommend backing up your database before upgrading.

If you'd like to enable multitenancy, check the multitenancy documentation.

If you enable this feature, it's also strongly recommended that you include a task in your CI to ensure the integrity of your schema.rb file. An example workflow for GitHub Actions is included in this release (see pull request 5009).

⚠️ When upgrading your development environment, update your config/database.yml file and add the line schema_search_path: "public,shared_extensions" (you can copy it from the config/database.yml.example file). This is done automatically on production environments when running the consul:execute_release_tasks rake task.

⚠️ We've removed the url configuration option in the administration settings. If you're using Setting["url"] in your custom code, replace it with either root_url (if the code is executed during a request) or with root_url(ActionMailer::Base.default_url_options) (if the code is executed during a rake task or a delayed job).

⚠️ DelayedJob processes now create processes which monitor and restart DelayedJob processes in case they crash (see pull request #5146). If you're already monitoring these processes with tools like monit or systemd, you might want to disable this feature. Also note that, in order to stop delayed job, we now need to pass the -n option: RAILS_ENV=production bin/delayed_job -n 2 stop.

⚠️ Other than the standard production, development and test environments, Consul Democracy offers the option to setup both staging and preproduction environments. If you're using the preproduction environment (which is not the staging environment), note we're now using the same configuration for preproduction and staging environments. If your config/environments/preproduction.rb is not identical to your config/environments/staging.rb, you'll have to change the former in order to include the differences (or you can also choose to base it on your production environment instead). If you're using the staging environment but not the preproduction one (or you aren't using either of them), ignore this warning.