e1359714cc
|
||
|---|---|---|
| build | ||
| inquirey | ||
| offline | ||
| route_sql | ||
| .env.sample | ||
| .gitignore | ||
| LICENSE | ||
| Master Template 1.6.xlsm | ||
| README.md | ||
| columns.md | ||
| create_certs.sh | ||
| forecast_api.service | ||
| index.js | ||
| msauth.html | ||
| package-lock.json | ||
| package.json | ||
| sample_request.json | ||
README.md
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 .envand 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
additionally, to setup as service
- copy .service file to //etc/systemd/system/ (adjust user/working direct if needed)
sudo systemctl enable forecast_api.service
Initial Forecast
- all SQL depends on unchanged core sales matrix table schema