Go to file
PhilRunninger 86225ea7e5 Get pounds to update for each forecast adjustment.
Lots of cleanup here too, removing large swaths of code that are no
longer needed. Many improvements the Excel workbook, which is kept in
Teams, not git. These changes may or may not have had accompanying VBA
changes.
2023-04-27 16:54:37 -04:00
VBA Get pounds to update for each forecast adjustment. 2023-04-27 16:54:37 -04:00
build Get pounds to update for each forecast adjustment. 2023-04-27 16:54:37 -04:00
inquirey swap everything for a 2109 baseline 2023-03-07 16:45:55 -05:00
offline Switch source table from rlarp.itemmv to "CMS.CUSLG".itemm 2023-03-01 17:55:30 -05:00
route_sql Get pounds to update for each forecast adjustment. 2023-04-27 16:54:37 -04:00
.env.sample populate sample env 2020-02-11 11:06:13 -05:00
.gitignore include pool ddl 2023-02-15 14:21:49 -05:00
LICENSE Create LICENSE 2019-03-12 14:31:39 -04:00
Master Template.xlsm save my version that was on teams as 1.7 2023-03-03 14:32:10 -05:00
README.md Update README.md 2021-07-12 14:44:56 -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 updates 2023-02-24 19:28:14 -05:00
index.js Get pounds to update for each forecast adjustment. 2023-04-27 16:54:37 -04:00
msauth.html change header 2019-03-19 00:13:12 -04:00
package-lock.json Upgrade packages for use in node version 19.5.0. 2023-02-17 14:22:05 -05:00
package.json Upgrade packages for use in node version 19.5.0. 2023-02-17 14:22:05 -05: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