Record HotView development loop
This commit is contained in:
@@ -1,5 +1,9 @@
|
|||||||
# Changelog
|
# Changelog
|
||||||
|
|
||||||
|
## Unreleased
|
||||||
|
|
||||||
|
- Recorded the active development direction: use the local HotView/hot-reload setup for iterative app work and defer web/local builds and hosted deployment unless explicitly requested.
|
||||||
|
|
||||||
## 0.1.31 - 2026-07-15
|
## 0.1.31 - 2026-07-15
|
||||||
|
|
||||||
- Started Phase 3 deploy-from-Gitea hardening by making the hosted deploy script refuse dirty or unpushed Libre Study and LibreBible data repos.
|
- Started Phase 3 deploy-from-Gitea hardening by making the hosted deploy script refuse dirty or unpushed Libre Study and LibreBible data repos.
|
||||||
|
|||||||
+3
-1
@@ -19,7 +19,9 @@ This does not require a permanent code fork right now. Prefer one shared app wit
|
|||||||
|
|
||||||
## Workflow Rule
|
## Workflow Rule
|
||||||
|
|
||||||
Keep the workflow simple and durable:
|
Current active workflow note: while the app is being shaped interactively, use the local HotView/hot-reload setup as the primary test loop. Do not spend cycles on web builds, local builds, installer builds, or hosted deployment unless the user explicitly asks for a release/deploy pass. Hosted deployment remains a later/manual milestone, not the everyday development loop.
|
||||||
|
|
||||||
|
Keep the durable release workflow simple when it is time to publish:
|
||||||
|
|
||||||
1. Develop locally in `W:\libre-study` and `W:\libre-bible-data`.
|
1. Develop locally in `W:\libre-study` and `W:\libre-bible-data`.
|
||||||
2. Commit locally.
|
2. Commit locally.
|
||||||
|
|||||||
Reference in New Issue
Block a user