84a88ee1fb
We remove our custom puma.service.erb template located at lib/capistrano/templates, as the upstream capistrano3-puma gem (v6.2.0) now supports all the adjustments we previously needed. This template was originally copied and modified in PR #5842 (Bump capistrano3-puma from 5.2.0 to 6.0.0), with the following relevant changes: 1. WatchdogSec=0 We disabled systemd's watchdog feature by setting WatchdogSec=0. This is now covered upstream since v6.1.0 via: > <% if fetch(:puma_systemd_watchdog_sec) && fetch(:puma_systemd_watchdog_sec) > 0 %> > WatchdogSec=<%= fetch(:puma_systemd_watchdog_sec) %> > <% end %> To preserve the same behavior, we now explicitly set: > set :puma_systemd_watchdog_sec, 0 in config/deploy.rb, instead of relying on the template override. 2. SyslogIdentifier=puma In our custom template, we replaced the default line: > SyslogIdentifier=<%= fetch(:puma_service_unit_name) %> with: > SyslogIdentifier=puma This was done to avoid introducing a new config variable in the installer. However, now that we want to remove the overridden template, we must accept the default behavior from the gem: > set :puma_service_unit_name, -> { "puma_#{fetch(:application)}_#{fetch(:stage)}" } As a result, the generated SyslogIdentifier will change from "puma" to something like "puma_consul_staging". The only implication is that we'll open a PR in the installer to replace the hardcoded "puma" with the dynamic default, so everything stays consistent. Another option would be to override puma_service_unit_name with "puma" to keep the SyslogIdentifier exactly as before. However, this would also affect the names of the systemd services and sockets (e.g., puma.service instead of puma_consul_staging.service), which may lead to conflicts or require manual cleanup steps like disabling and removing the old units. For now, we prefer to avoid that. 3. After=network.target We had removed the "syslog.target" from the "After=" directive, as we didn't depend on syslog. However, keeping "After=syslog.target network.target" does not negatively impact us, since Puma logs to files directly using StandardOutput=append:.... So we can also adopt the default value from template here. 4. ExecStart In version 6.2.0, a small change was made to the template logic for the ExecStart line. This change does not affect us. Since we don't define puma_use_login_shell, the behavior remains exactly the same as before. With these changes already supported in the gem, we no longer need a local copy of the puma service template.
CONSUL DEMOCRACY
Citizen Participation and Open Government Application
This is the opensource code repository of the eParticipation website CONSUL DEMOCRACY, originally developed for the Madrid City government eParticipation website, and currently maintained by the open source software community in collaboration with the CONSUL DEMOCRACY Foundation.
Documentation
Check the ongoing documentation to learn more about how to start your own CONSUL DEMOCRACY fork, install it, customize it and learn to use it as an administrator/maintainer.
CONSUL DEMOCRACY Foundation and project website
You can access the main website of the project at http://consuldemocracy.org where you can find information about the use of the platform, the CONSUL DEMOCRACY Foundation, the global community of users and local partners, news, and ways to get more support or get in touch.
Configuration for development and test environments
NOTE: The installation process will vary depending on your operating system. Please make sure to follow the Local Installation Guide appropriate for your OS.
Prerequisites: install git, Ruby 3.3.8, CMake, pkg-config, Node.js 20.19.2, ImageMagick and PostgreSQL (>=9.5).
Note: The bin/setup command below might fail if you've configured a username and password for PostgreSQL. If that's the case, edit the lines containing username: and password: (adding your credentials) in the config/database.yml file and run bin/setup again.
git clone https://github.com/consuldemocracy/consuldemocracy.git
cd consuldemocracy
bin/setup
bin/rake db:dev_seed
Run the app locally:
bin/rails s
You can run the tests with:
bin/rspec
Note: running the whole test suite on your machine might take more than an hour, so it's strongly recommended that you setup a Continuous Integration system in order to run them using parallel jobs every time you open or modify a pull request (if you use GitHub Actions or GitLab CI, this is already configured in .github/workflows/tests.yml and .gitlab-ci.yml) and only run tests related to your current task while developing on your machine. When you configure the application for the first time, it's recommended that you run at least one test in spec/models/ and one test in spec/system/ to check your machine is properly configured to run the tests.
You can use the default admin user from the seeds file:
user: admin@consul.dev pass: 12345678
But for some actions like voting, you will need a verified user, the seeds file also includes one:
user: verified@consul.dev pass: 12345678
Configuration for production environments
See installer
Current state
Development started on 2015 July 15th. Code was deployed to production on 2015 september 7th to decide.madrid.es. Since then new features are added often. You can take a look at the current features at the project's website and future features at the Roadmap and open issues list.
License
Code published under AFFERO GPL v3 (see LICENSE-AGPLv3.txt)
Contributions
See CONTRIBUTING.md