Harden hosted deploy source checks
This commit is contained in:
+5
-3
@@ -98,12 +98,14 @@ Definition of done:
|
||||
|
||||
Goal: make local changes flow predictably to the live app through Git.
|
||||
|
||||
Current foundation note: the hosted deploy script now verifies that both Libre Study and LibreBible data are clean and equal to `origin/main` before it builds or publishes, and records both deployed commit hashes in deploy metadata.
|
||||
|
||||
Tasks:
|
||||
|
||||
- Keep Christ Unscripted Gitea as the remote source of truth for deployable code.
|
||||
- Add a deployment script that pulls or receives the pushed commit, installs/builds as needed, and publishes the web build.
|
||||
- Record the deployed commit hash somewhere visible or inspectable.
|
||||
- Decide whether deploys are manual first, then later automatic after push.
|
||||
- Add a deployment script that pulls or receives the pushed commit, installs/builds as needed, and publishes the web build. Started with a manual script that only deploys clean `origin/main` state.
|
||||
- Record the deployed commit hash somewhere visible or inspectable. Started with `deploy-info.json`, including both app and LibreBible data commits.
|
||||
- Decide whether deploys are manual first, then later automatic after push. Manual deploy remains the current private-alpha default.
|
||||
- Keep LibreBible package generation/deployment separate from Libre Study app deployment, but make the app consume the deployed package catalog.
|
||||
|
||||
Definition of done:
|
||||
|
||||
Reference in New Issue
Block a user