Energy Sparks is an open source application that is designed to help schools improve their energy efficiency.
The application collects and presents gas and electricity usage data in a way that is accessible to staff, students and parents. Supported by educational resources, the application will support teachers in helping children understand more about energy usage, how to be more efficient and see how actions they take in the school, e.g. switching off lighting, has an effect on usage.
Combining access to data, the ability to log interventions and a competitive element between schools, the goal is to not just save schools money in reducing energy consumption through long term changes, it is hoped that the application will also help educate children about what it means to be energy efficient.
The application is open source and is powered by open data. It is being designed to be easily deploy and run for minimal cost, allowing it to be run by local councils and/or community groups around the UK.
The initial prototype application and user testing is being carried out in Bath & North East Somerset. The work is a joint project between Bath: Hacked, Transition Bath, Resource Futures and B&NES council.
The project has been funded by an award from the Open Data Institute summer showcase 2016.
Development of the application and documentation is in progress. Please check back later for more information.
For now you may wish to read the evolving documentation in the project wiki.
The application is a Rails 5.2, Ruby 2.5.1 project.
Read the CONTRIBUTING.md guidelines for how to get started.
Development mode uses mail catcher for sending mails - you need to install the mailcatcher gem for this to work correctly.
Setting up a new test environment
- Set up appropriate database in RDS - make sure the password doesn't have any (or too many) special characters, best to keep to digits and letters if possible!
- Use pg_dump to get dump of current production database
- Use psql to get data into new database
- Clone production environment
- Update environment variables to point at new database, plus the various other test things like rollbar
- add the EC2 security group for the new machine to the RDS security section