fe9da7988f
As it seems that adding complexity to the password is something that might be wanted from the Consul applications, we added the necessary changes to allow it. In this version we simply: - Uncomment the configuration variable "password_complexity" - Set this variable without any restrictions - Adapt the application so that everything still works normally. One of the things that had to be done to adapt the application was to remove the overwriting of the "self.included" method. The original idea of overwriting the "self.included" method seems to be the possibility of being able to overwrite the :current_equal_password_validation validation. The problem comes from the fact that by only calling that validation, the rest of the validations that are defined (in this case "password_complexity") are no longer applied. It seems like a good idea to remove the overwrite of the "self.included" method to allow all the defined validations to be applied and simply overwrite the :current_equal_password_validation method so that everything behaves the same. :allow_passwords_equal_to_email configuration has been enabled too, in order to allow existing records with this configuration. Another change made was to uncomment the line: and to keep everything working the same set the value to false: config.email_validation = false. This change has had to be made because in the documentation of devise-security it says the following: In other words, if we want to use the :secure_validatable module we have to enable this configuration even if its value is "false". If we kept the configuration variable commented out: The following error appears: "uninitialized constant Devise::Models::SecureValidatable::EmailValidator". So it has been verified that if before making any change we decommented the line and added the value of "false", the application worked as normal.
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 docs
Prerequisites: install git, Ruby 3.1.4, CMake, pkg-config, shared-mime-info, Node.js 18.18.2 and PostgreSQL (>=9.5).
git clone https://github.com/consuldemocracy/consuldemocracy.git
cd consuldemocracy
bin/setup
bin/rake db:dev_seed
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