bot/WeatherTool
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refine production workspace layouts

Browse Source
This commit is contained in:
b0txec
2026-08-19 10:38:25 +03:00
parent 9147342686
commit fd1c0148b6
5 changed files with 95 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/DEVELOPMENT_AND_STAGING.md
+7 -28
View File
@@ -4,8 +4,9 @@
| Environment | Purpose | Address |
|---|---|---|
| Windows | Source editing, local Docker build, and initial testing | `http://localhost:9190` |
| Rocky Linux | Production-like isolated staging | `http://192.168.1.101:9190` |
| Windows | Source editing and Git workflow only | Not applicable |
| Rocky Linux | Docker development and production-like staging | `http://192.168.1.101:9190` |
| Future VPS | Planned deployment environment | Not provisioned yet |
| Workplace production | Out of scope until reviewed and approved | Not documented here |
Rocky checkout:
@@ -37,30 +38,9 @@ codex/staging-baseline
## Windows development
Build the frontend using the project Node container:
```powershell
docker compose run --rm node
```
Start or update the complete local stack when backend or Compose changes require it:
```powershell
docker compose up --build -d
```
Seed deterministic observations:
```powershell
docker compose --profile tools run --rm seed
```
Inspect status and logs:
```powershell
docker compose ps
docker compose logs --tail 100 scala
```
Use Windows to edit and review source files and to create Git commits. Docker builds,
the running application, synthetic-data operations, and browser testing belong on
Rocky. Docker Desktop is not part of the normal project workflow.
## Commit and transfer workflow
@@ -126,9 +106,8 @@ Prefer a normal Git revert rather than manually copying old files:
1. Identify the faulty commit with `git log --oneline`.
2. On the development checkout, run `git revert <commit>`.
3. Build and test the reverted state locally.
3. Push the revert and build and test it on Rocky.
4. Push the revert commit.
5. Pull it on Rocky and run the appropriate frontend-only or full-stack deployment command.
Database rollback is a separate operation and must not be inferred from a source rollback. Database backup and restore procedures are not yet defined.