cf6d9ce753
Since Bundler 2.4.19, including in Ruby 3.2.3, it's possible to define the Ruby version in the Gemfile by indicating which file contains the version [1]. There are at least two practical cases where this is an advantage. First, people using RVM in development will no longer accidentally run the application using the wrong Ruby version (which, before these changes, might happen if they switch to a branch using a different Ruby version and forget to run `rvm use` or exit the current folder and enter it again) because they will get an error when trying to do so. Second, people using services like Heroku no longer need to modify the Gemfile. The disadvantage is that, now, every time we update the Ruby version, we have to remember to run `bundle` so our `Gemfile.lock` gets the new version. [1] https://github.com/rubygems/rubygems/releases/tag/bundler-v2.4.19
CONSUL DEMOCRACY
Citizen Participation and Open Government Application
CONSUL DEMOCRACY Project main website
You can access the main website of the project at http://consuldemocracy.org where you can find documentation about the use of the platform, videos, and links to the community space.
Configuration for development and test environments
NOTE: For more detailed instructions, check the local installation docs.
Prerequisites: install git, Ruby 3.2.5, CMake, pkg-config, Node.js 18.20.3, 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
License
Code published under AFFERO GPL v3 (see LICENSE-AGPLv3.txt)
Contributions
See CONTRIBUTING.md