31 lines
1.4 KiB
Markdown
31 lines
1.4 KiB
Markdown
# Gitea Deployment Toolkit
|
|
|
|
Versioned Gitea Actions templates and composite actions for:
|
|
|
|
- Laravel deployment to a 1Panel PHP 8.2 runtime
|
|
- Taro WeChat Mini Program preview publishing
|
|
|
|
## Compatibility
|
|
|
|
Gitea 1.22 does not provide Scoped Workflows or the `concurrency` key. Copy a workflow from `workflows/` into the consuming repository's `.gitea/workflows/` directory, then reference the versioned actions in this repository. The Laravel action uses a host `flock` lock to serialize release changes.
|
|
|
|
Gitea 1.22 may automatically cancel an older push workflow when a newer commit reaches the same branch. Upgrade to Gitea 1.26 or newer before relying on configurable workflow concurrency. The deployment script traps termination and restores the previous code link, but an infrastructure-level forced kill can still interrupt a migration.
|
|
|
|
## Versioning
|
|
|
|
Consumers should reference the stable major tag:
|
|
|
|
```yaml
|
|
uses: https://gitea.neatcn.com/pets/deployment-toolkit/actions/laravel-release@v1
|
|
```
|
|
|
|
Create immutable release tags such as `v1.0.0`, then move `v1` only after validation.
|
|
|
|
## Security
|
|
|
|
- Store credentials in consuming-repository Secrets.
|
|
- Keep production `.env` files on the target server.
|
|
- Restrict production Runner labels to trusted repositories.
|
|
- Never expose a Docker socket to pull-request jobs.
|
|
- Pin third-party actions after the first successful bootstrap.
|