Jesse/Skill
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update deployment preflight guidance

Browse Source
This commit is contained in:
Jesse
2026-08-06 08:41:30 +00:00
parent c2ad676190
commit 8201138038
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy-company-linux/SKILL.md
+5 -4
View File
@@ -14,15 +14,16 @@ Deploy applications to the company Linux host through SSH with release directori
3. Prefer an existing `compose.yaml`, `compose.yml`, `docker-compose.yaml`, or `docker-compose.yml`. Use Dockerfile mode only when no Compose configuration exists. 3. Prefer an existing `compose.yaml`, `compose.yml`, `docker-compose.yaml`, or `docker-compose.yml`. Use Dockerfile mode only when no Compose configuration exists.
4. Derive a lowercase app name that starts with a letter or digit and contains only letters, digits, underscores, and hyphens. Do not reuse an existing application name unless the user is updating that application. 4. Derive a lowercase app name that starts with a letter or digit and contains only letters, digits, underscores, and hyphens. Do not reuse an existing application name unless the user is updating that application.
5. Detect port collisions against the server profile and a live preflight. Ask only when the intended application name, public port, or health endpoint cannot be inferred safely. 5. Detect port collisions against the server profile and a live preflight. Ask only when the intended application name, public port, or health endpoint cannot be inferred safely.
6. Authenticate with an SSH key. If key authentication is unavailable, use `COMPANY_LINUX_PASSWORD` only for the current process. Never write a password into the skill, repository, deployment archive, command output, or shell history. 6. Check whether every Docker base image is cached before deploying. The server may be unable to reach Docker Hub; for Node.js projects, prefer the server's cached `local/node:24.16.0-bookworm` image when appropriate.
7. Run preflight before deployment: 7. Authenticate with an SSH key. If key authentication is unavailable, use `COMPANY_LINUX_PASSWORD` only for the current process. Never write a password into the skill, repository, deployment archive, command output, or shell history.
8. Run preflight before deployment:
```powershell ```powershell
powershell -ExecutionPolicy Bypass -File scripts/deploy.ps1 ` powershell -ExecutionPolicy Bypass -File scripts/deploy.ps1 `
-Action preflight -AppName <app-name> -Action preflight -AppName <app-name>
``` ```
8. Deploy from the project root: 9. Deploy from the project root:
```powershell ```powershell
powershell -ExecutionPolicy Bypass -File scripts/deploy.ps1 ` powershell -ExecutionPolicy Bypass -File scripts/deploy.ps1 `
@@ -31,7 +32,7 @@ Deploy applications to the company Linux host through SSH with release directori
-HealthUrl <remote-health-url> -HealthUrl <remote-health-url>
``` ```
9. Report the release path, containers, exposed endpoint, and health result. If the command fails, report whether automatic rollback succeeded and include the smallest relevant log excerpt. 10. Report the release path, containers, exposed endpoint, and health result. If the command fails, report whether automatic rollback succeeded and include the smallest relevant log excerpt.
## Authentication Setup ## Authentication Setup