amiirkhl/my-protfolio
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci: align deployment workflow with Gitea
Some checks failed
Test and deploy / Verify production build (push) Has been cancelled
Details
Test and deploy / Deploy production (push) Has been cancelled
Details

Browse Source 
Use native Gitea contexts, audit the full dependency tree, and document the runner and branch-protection requirements needed for reliable deployments.
This commit is contained in:
Amirhossein Khalili
2026-09-10 11:04:12 +03:30
parent 9a778653cf
commit b4426400f3
2 changed files with 22 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
DEPLOYMENT.md
View File

@@ -9,6 +9,18 @@ Releases are stored in `<DEPLOY_PATH>/releases/<commit-sha>`. The `current`
symlink is changed only after the new container is healthy. If startup fails,
the deployment script automatically rebuilds and starts the previous release.
## Gitea Actions setup
Enable **Repository Actions** in the repository settings and register a trusted
Gitea Runner. The workflow uses the `ubuntu-latest` label; that runner image must
provide Bash, Git, `tar`, OpenSSH (`ssh` and `scp`), and standard GNU utilities.
Node.js 22 is installed by the workflow.
After the first successful verification run, protect `main` in Gitea and make
the **Verify production build** status check required. This prevents a pull
request from merging when linting, type-checking, tests, the production build,
or the dependency audit fails.
## Gitea repository secrets
Add these secrets under the repository's **Settings > Actions > Secrets**: