store packages to getia registry

DEPLOYMENT_FILES.md

@@ -32,3 +32,23 @@ Excluded:
 - runtime cache, logs, sessions, uploads, and generated reports
 
 The server keeps its own `.env` and runtime `writable/` contents. The deploy job syncs from `build/deploy/` and excludes mutable writable subdirectories so production data is not overwritten.
+
+## Gitea Package
+
+The deploy workflow also archives `build/deploy/` and publishes it to Gitea Packages as a generic package:
+
+- Package name: `alrahma_sunday_school`
+- Version format: `{branch}-{run_number}-{short_sha}`
+- File format: `alrahma_sunday_school-{version}.tar.gz`
+
+Required repository secrets for package publishing:
+
+- `GITEA_PACKAGE_USER`
+- `GITEA_PACKAGE_TOKEN`
+
+Optional repository secrets:
+
+- `GITEA_BASE_URL` - defaults to the Actions server URL.
+- `GITEA_PACKAGE_OWNER` - defaults to the repository owner.
+
+The token must have permission to publish packages for the package owner.