pt/forecast_api
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
477 Commits 2 Branches 15 Tags 46 MiB
VBA 48.7%
PLpgSQL 42.6%
JavaScript 6.9%
HTML 1.7%
Shell 0.1%
3b72871cc6
Go to file
PhilRunninger 3b72871cc6 Renamed the pivot tables, and simplified some code. 
I made the "did I double click in the pivot table?" code work more
efficiently.
2023-02-28 15:05:54 -05:00
build increment snapshot period 2021-07-30 08:15:48 -04:00
inquirey get rid of old months inquirey 2021-07-14 15:46:38 -04:00
offline move inquiries to their own folder 2021-07-12 10:52:25 -04:00
route_sql Updates to the newest season in scenario_package.sql 2023-02-27 16:15:35 -05:00
.env.sample populate sample env 2020-02-11 11:06:13 -05:00
.gitignore ignore new dbeaver folder 2021-07-14 15:47:22 -04:00
columns.md add substance column and move some files out of the route folder that aren't actually being used by routes 2020-02-19 13:25:28 -05:00
create_certs.sh add pieces to get the server running 2020-02-05 23:41:57 -05:00
forecast_api.service add slash for directory 2021-04-05 19:03:00 +00:00
index.js add a floor date to prevent adjusting actual history based on the supplied timestamp 2021-07-16 10:20:32 -04:00
LICENSE Create LICENSE 2019-03-12 14:31:39 -04:00
Master Template.xlsm Renamed the pivot tables, and simplified some code. 2023-02-28 15:05:54 -05:00
msauth.html change header 2019-03-19 00:13:12 -04:00
package-lock.json add pieces to get the server running 2020-02-05 23:41:57 -05:00
package.json upgrade packages 2020-02-06 00:09:36 -05:00
README.md Update README.md 2021-07-12 14:44:56 -04:00
sample_request.json move files around 2020-02-19 17:05:27 -05:00

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 .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

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