Compare commits

..

No commits in common. "73c3171d0440d1433dc31e4c6e34b709f6f82d0c" and "a5dc4aaa8582713c66872923a4f1822f6d1cfa8d" have entirely different histories.

View File

@ -1,14 +1,10 @@
This will not work without exactly the right database schema which is out of scope. this is only the running process part of the forecast.
## Setup
* git clone (to //opt for verbatim use of the .service file)
* `npm install`
* create certs: `chmod 700 create_certs.sh` , `./create_certs.sh`
* clone sample env `cp .env.sample .env` and specify 1) database creds 2) working directory 3) listening port
* run: `node index.js`
* navigate to `https://localhost:8080/` to valide it's connectable
* open the spreadsheet and specify the target connection
* create .env from template .env.sample sepcifiying database creds and listening port for API, and working directory
* `node index.js`
additionally, to setup as service
* copy .service file to //etc/systemd/system/ (adjust user/working direct if needed)