move to production server
- Dominant language
- KRL
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The proof of concept is currently running on a work station. The entire line of code needs to be moved (or copied?) onto the production server. This is the file server machine, which contains the data files used in production.
1. The production data files need to be there (EM)
2. The report to produce TXT files needs to be in every workstation STR file (EM)
3. A production vDOS script needs to call for that report to run under vDOS in its `autoexec.bat` file (EM)
4. A pico-engine needs to be running that contains order updates information
5. A `watch-updates.js` file needs to be running, watching for changes in the TXT files and signaling events to the picos
6. The pico rulesets need to be adapted as needed to run in the production environment
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by documenting how the proof of concept currently runs on the workstation and inventory the production data files, workstation STR files, vDOS autoexec.bat, pico-engine, pico rulesets, and watch-updates.js. Verify each of the six listed production requirements and define completion as the report, update watcher, engine, and adapted rulesets running together against the production data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100