Просмотр исходного кода

ci: add safe IIS release deployment pipeline

ci-iis-release-pipeline
Clawdbot 7 часов назад
Родитель
Сommit
3fe93f7bdb
1 измененных файлов: 6 добавлений и 0 удалений
  1. +6
    -0
      README.md

+ 6
- 0
README.md Просмотреть файл

@@ -77,6 +77,12 @@ Move generated file to `app/controllers/`.
- IIS URL Rewrite module - IIS URL Rewrite module
- Microsoft Access Database Engine (for .accdb support) - Microsoft Access Database Engine (for .accdb support)


## Deployment

Production deployment uses full-repository immutable release directories while IIS points only at each release's `public/` directory. `scripts/deploy-iis-git.ps1` packages and transfers a reviewed checkout to `webserver-1` over Tailscale/OpenSSH; `scripts/install-iis-release.ps1` performs host preflight, preserves the machine-owned `public/web.config`, enables Classic ASP parent paths, switches releases, smoke tests, and supports rollback. Database migrations are disabled by default.

Gitea 1.11.4 has no Gitea Actions, so run the controller script from a trusted external CI worker or operator workstation. Start with `-DryRun`, which makes no network connection. See [docs/deployment-guide.md](docs/deployment-guide.md) and [docs/deployment-configuration.md](docs/deployment-configuration.md).

## Testing ## Testing


This repo now includes a dev-only `aspunit` harness under `tests/`. It is intentionally separate from the production app rooted at `public/`. This repo now includes a dev-only `aspunit` harness under `tests/`. It is intentionally separate from the production app rooted at `public/`.


Загрузка…
Отмена
Сохранить

Powered by TurnKey Linux.