6e5ef9795e
In commit96ae69fe9, we stopped using cookies to track Ahoy visits and started using a combination of the IP and the browser agent instead. However, since we're still using the legacy logic from Ahoy 1.x to track visits (which we had to add in commitb5220effd), this way of tracking visits doesn't work and counts every page visited by a user as an independent visit. Maybe we could migrate existing data, which uses the `visitor_id` column so it uses the new `visit_token` and `visitor_token` columns, but there's no mention in the Ahoy documentation regarding how to do so. While deciding what to do about this, we found something interesting. For two years, we've been seeing random failures in the `system/admin/tenants_spec.rb` tests, with messages like: ``` 1) Tenants Create Tenant with subdomain Failure/Error: raise TenantNotFound, <<~EXCEPTION_MESSAGE Could not set search path to schemas, they may be invalid: "#{tenant}" #{full_search_path}. Original error: #{exception.class}: #{exception} EXCEPTION_MESSAGE Apartment::TenantNotFound: Could not set search path to schemas, they may be invalid: "earth" "public", "shared_extensions". Original error: ActiveRecord::StatementInvalid: Could not find schema earth ``` And we've found one of the causes: the AJAX requests done by Ahoy to track visits. Sometimes a test that creates or updates a tenant finishes but the Ahoy AJAX request to, say, `earth.lvh.me/ahoy/visits`, is handled by the next test, when the `earth` schema no longer exists, thus raising an `Apartment::TenantNotFound` exception. So by disabling these AJAX requests and tracking the visits in the server instead, we're killing two birds in one stone: we're fixing the bug regarding the visits count and we're reducing the flakiness in our test suite. It looks like we're also removing the "phantom ahoy cookie" we were getting since the mentioned commitb5220effd: an ahoy cookie was quickly set and unset in the browser. Note that, even though we aren't migrating any data, we're still adding the new fields, because some tests started to fail because, when tracking visits in the server without cookies, Ahoy expects the Visit model to have a `visit_token` field.
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: 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
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