0214184b2d
In the previous commit I mentioned: > If I'm right, the `investment_votes` instance variable only exists to > avoid several database queries to get whether the current user has > supported each of the investments. > > However, that doesn't make much sense when only one investment is > shown. Now let's discuss the case when there are several investments, like in the investments index: * There are 10 investments per page by default * Each query takes less than a millisecond * We still make a query per investment to check whether the current user voted in a different group * AFAIK, there have been no performance tests showing these optimizations make the request to the investments index significantly faster * These optimizations make the code way more complex than it is without them Considering all these points, I'm removing the optimizations. I'm fine with adding `includes` calls to preload records and avoid N+1 queries even if there are no performance tests showing they make the application faster because the effect on the code complexity is negligible. But that's not the case here. Note we're using `defined?` instead of the `||=` operator because the `||=` operator will not serve its purpose when the result of the operation returns `false`.
CONSUL
Citizen Participation and Open Government Application
This is the opensource code repository of the eParticipation website CONSUL, originally developed for the Madrid City government eParticipation website
Documentation
Check the ongoing documentation at https://docs.consulproject.org to learn more about how to start your own CONSUL fork, install it, customize it and learn to use it from an administrator/maintainer perspective.
CONSUL Project main website
You can access the main website of the project at http://consulproject.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 docs
Prerequisites: install git, Ruby 2.6.7, CMake, pkg-config, shared-mime-info, Node.js and PostgreSQL (>=9.5).
git clone https://github.com/consul/consul.git
cd consul
bundle install
cp config/database.yml.example config/database.yml
cp config/secrets.yml.example config/secrets.yml
bin/rake db:create
bin/rake db:migrate
bin/rake db:dev_seed
RAILS_ENV=test rake db:setup
Run the app locally:
bin/rails s
Run the tests with:
bin/rspec
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