bunny-lab/Borealis-Github-Replica
1
0
Fork 0
mirror of https://github.com/bunny-lab-io/Borealis.git synced 2025-10-26 15:41:58 -06:00
Code Issues Packages Projects Releases Wiki Activity

Add Engine requirements for launcher deployment

Browse Source
This commit is contained in:
Nicole Rappe
2025-10-22 16:10:03 -06:00
parent 4b22fe61ca
commit 438c7e1ed9
3 changed files with 19 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Data/Engine/CURRENT_STAGE.md
View File

@@ -60,10 +60,8 @@
- 11.3 Commit after integration tests (or mocked unit tests) confirm API workflows.
[IN PROGRESS] 12. Final parity verification
- 12.1 Follow the staging playbook in `Data/Engine/STAGING_GUIDE.md` to stand up the Engine end-to-end and exercise enrollment,
token refresh, agent connections, GitHub integration, and scheduler flows.
- 12.1 Follow the staging playbook in `Data/Engine/STAGING_GUIDE.md` to stand up the Engine end-to-end and exercise enrollment, token refresh, agent connections, GitHub integration, and scheduler flows.
- 12.2 Record any divergences in the staging guide’s table and address them with follow-up commits before cut-over.
- 12.3 Once parity is confirmed, coordinate entrypoint switching (point deployment at `Data/Engine/bootstrapper.py`) and plan
the legacy server deprecation.
- Supporting documentation and unit tests live in `Data/Engine/README.md`, `Data/Engine/STAGING_GUIDE.md`, and
`Data/Engine/tests/` to guide the remaining staging work.
- 12.3 Once parity is confirmed, coordinate entrypoint switching (point deployment at `Data/Engine/bootstrapper.py`) and plan the legacy server deprecation.
- Supporting documentation and unit tests live in `Data/Engine/README.md`, `Data/Engine/STAGING_GUIDE.md`, and `Data/Engine/tests/` to guide the remaining staging work.
- Engine deployment now installs dependencies via `Data/Engine/requirements.txt` so parity runs include Flask, Socket.IO, and security packages.

4
Data/Engine/README.md
View File

@@ -65,6 +65,10 @@ The Engine mirrors the legacy defaults so it can boot without additional configu
As migration continues, services, repositories, interfaces, and integrations will live under their respective subpackages while maintaining isolation from the legacy server.
## Python dependencies
`Data/Engine/requirements.txt` mirrors the minimal runtime stack (Flask, Flask-SocketIO, CORS, requests, PyJWT, and cryptography) needed by the Engine entrypoint. The PowerShell launcher consumes this file when preparing the `Engine/` virtual environment so parity tests always run against an environment with the expected web and security packages preinstalled.
## HTTP interfaces
The Engine now exposes working HTTP routes alongside the remaining scaffolding:

11
Data/Engine/requirements.txt Normal file
View File

@@ -0,0 +1,11 @@
#////////// PROJECT FILE SEPARATION LINE ////////// CODE AFTER THIS LINE ARE FROM: <ProjectRoot>/Data/Engine/requirements.txt
# Core web stack
Flask
flask_socketio
flask-cors
eventlet
requests
# Auth & security
PyJWT[crypto]
cryptography