22c2375f44
It's not completely seamless, but it should work adequately well. The workbook (aka client) inserts the workbook version into the http request body. The server code compares that version number against its minimum supported client version. If the client is too old, an error message is sent back to the client. When the client receives the "Obsolete" error message, it launches the https://<server>:<port>/template URL in the default browser, which enables the user to save the downloaded new workbook file. |
||
|---|---|---|
| build | ||
| inquirey | ||
| Master Template.xlsm_EXPORTS | ||
| offline | ||
| route_sql | ||
| VBA | ||
| .env.sample | ||
| .gitignore | ||
| columns.md | ||
| create_certs.sh | ||
| forecast_api.service | ||
| index.js | ||
| LICENSE | ||
| Master Template.xlsm | ||
| msauth.html | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| sample_request.json | ||
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