Solar Array and home energy dashboard.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
John-Mark Gurney fdbe40fee2 Merge branch 'master' of ssh://git.funkthat.com:822/jmg/solardash 4 years ago
root add some experiemental code wrt stacking... 4 years ago
solardash make sure to handle the first data w/ NaN's.. 4 years ago
.gitignore ignore the timzeone data.. 4 years ago
LICENSE.txt add license.. 4 years ago
Makefile this makes timezones work.. why this exact same code didn't work earlier 4 years ago
NOTES.md add link to range series to use.. 4 years ago
README.md add some info to the README.. 4 years ago
cmds.txt add another useful command.. 4 years ago
fakedata.py add some experiemental code wrt stacking... 4 years ago
requirements.txt bring in the start of the python daemon side of things 4 years ago
setup.py Merge branch 'master' of ssh://git.funkthat.com:822/jmg/solardash 4 years ago

README.md

Solar Dashboard

This is a solar dashboard for displaying information about a solar install.

Running

Running the program first involves setting up the environment via the command make env. This will setup a Python virtual environment and install the necessary pacakages.

Once the environment is setup, it can be configured by XXX.

To run the webserver, run the command make run, and that will launch a local webserver.

Structure

Frontend

The front end is located in root. The meat of the logic is in js/solardash.base.js. The testing infrastructure is in js/solardash.file.jspp as if you are launching the page from a file url, there is no way to make a url to access the backend.

Testing

Make sure that the environment is setup with the make env command before running the following commands.

For testing the frontend, if you have a window running the command make keepupdate running, when you edit various files, things will automatically be regenerated as necessary.

For testing the backend, have a window running the command make test. This will automaticaly run the various tests for the backend, and provide code coverage results.