Skip to content
Skills Library
DevOps & cloud · Automation

devopser-deploy

/devopser-deploy

Expert guidance for shipping the DevOpser self-evolving software template to a real environment or producing signed mobile artifacts. Covers target selection (Lightsail, Cloud Run, Fly, ECS Fargate, Kubernetes, VPS), AWS Secrets Manager in NODE_ENV=production, cross-account AssumeRole for multi-tenant hosting, and Android/iOS release builds. Triggers on "deploy this", "ship to Lightsail / Cloud Run / Fargate / Kubernetes", "wire up triggerDeployment", "cross-account trust role", "build the Android APK", "sign the iOS release".

Repository
devopser ↗
Licence
Apache-2.0
Last repository change
16.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
7
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 16.09.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Expert guidance for shipping the DevOpser self-evolving software template to a real environment or producing signed mobile artifacts. Covers target selection (Lightsail, Cloud Run, Fly, ECS Fargate, Kubernetes, VPS), AWS Secrets Manager in NODE_ENV=production, cross-account AssumeRole for multi-tenant hosting, and Android/iOS release builds. Triggers on "deploy this", "ship to Lightsail / Cloud Run / Fargate / Kubernetes", "wire up triggerDeployment", "cross-account trust role", "build the Android APK", "sign the iOS release".

Triggers from the description

deploy thisship to Lightsail / Cloud Run / Fargate / Kuberneteswire up triggerDeploymentcross-account trust rolebuild the Android APKsign the iOS release
Original author description

Expert guidance for shipping the DevOpser self-evolving software template to a real environment or producing signed mobile artifacts. Covers target selection (Lightsail, Cloud Run, Fly, ECS Fargate, Kubernetes, VPS), AWS Secrets Manager in NODE_ENV=production, cross-account AssumeRole for multi-tenant hosting, and Android/iOS release builds. Triggers on "deploy this", "ship to Lightsail / Cloud Run / Fargate / Kubernetes", "wire up triggerDeployment", "cross-account trust role", "build the Android APK", "sign the iOS release".

How it works

  1. Rules
  2. Key principles
  3. Quick reference
  4. Conflict resolution
Original SKILL.md headings · 37 lines, 338 words
SKILL.md preview
---
name: 'devopser-deploy'
description: Expert guidance for shipping the DevOpser self-evolving software template to a real environment or producing signed mobile artifacts. Covers target selection (Lightsail, Cloud Run, Fly, ECS Fargate, Kubernetes, VPS), AWS Secrets Manager in NODE_ENV=production, cross-account AssumeRole for multi-tenant hosting, and Android/iOS release builds. Triggers on "deploy this", "ship to Lightsail / Cloud Run / Fargate / Kubernetes", "wire up triggerDeployment", "cross-account trust role", "build the Android APK", "sign the iOS release".
license: Apache-2.0
metadata:
  author: DevOpser
  version: '1.0.0'
  workflow_type: 'advisory'
---

# DevOpser Deploy

Expert guidance for the **intentionally-blank deployment layer** of the DevOpser template, plus Capacitor Android/iOS release builds. This skill helps the agent pick a target, reason about multi-tenancy, wire the stub in `backend/routes/sites.js → triggerDeployment()`, and produce signed mobile artifacts using `./build-mobile.sh` and `./configure-android-signing.sh` — no new scripts added to the repo. Canonical playbook: [`AGENTS.md`](../../AGENTS.md) → **"Adding a deployment target"**.

## Rules

| Rule | Description |
|------|-------------|
| [target-selection](./rules/target-selection.md) | Decision matrix — Lightsail / Cloud Run / Fly / ECS Fargate / K8s / VPS, with a recommended default |
| [lightsail](./rules/lightsail.md) | Reference implementation — what DevOpser actually uses |
| [secrets-manager](./rules/secrets-manager.md) | The `NODE_ENV=production` pattern: secret names, not values |
| [cross-account](./rules/cross-account.md) | `CUSTOMER_CROSS_ACCOUNT_ROLE_ARN` + AssumeRole for multi-tenant managed hosting |
| [mobile-release](./rules/mobile-release.md) | Android keystore + `configure-android-signing.sh`, iOS via Xcode |

## Key principles

- **Defer to [`AGENTS.md`](../../AGENTS.md).** If this skill contradicts it, `AGENTS.md` wins — report the contradiction to DevOpser.
- **Ask the user exactly once** which target, which cloud relationship, and which tenant model before writing any IAC. Never guess — see [`target-selection.md`](./rules/target-selection.md).
- **No hardcoded account IDs, role names, or ARNs** in anything you commit. Env vars + a `customers` table, always.
- **Portability is non-negotiable.** The same code must run self-hosted *and* on managed hosting. Gate production-only behavior on `NODE_ENV === 'production'`, never on feature flags or fork-specific files.
- **Never commit `keystore.properties`, the keystore file, or `.env`.** The `.gitignore` already excludes them; do not add exceptions.

## Quick reference

| Situation | Go to |
|---|---|
| "Deploy this" with no more context | [`target-selection.md`](./rules/target-selection.md) → default recommendation |
| DevOpser's own hosting — you're building the reference impl | [`lightsail.md`](./rules/lightsail.md) |
| Moving from local dev to production, `MAIL_PASSWORD` breaks | [`secrets-manager.md`](./rules/secrets-manager.md) |
| Multi-tenant platform, each customer in their own AWS account | [`cross-account.md`](./rules/cross-account.md) |
| "Ship the Android app" / "build the iOS release" | [`mobile-release.md`](./rules/mobile-release.md) |

## Conflict resolution

If AGENTS.md contradicts this skill, AGENTS.md wins — report the contradiction to DevOpser.
Files in this package (7)
  • README.md 2 KB
  • SKILL.md 3 KB
  • rules/cross-account.md 6 KB
  • rules/lightsail.md 4 KB
  • rules/mobile-release.md 4 KB
  • rules/secrets-manager.md 4 KB
  • rules/target-selection.md 5 KB

Versions

The database has no other skills named devopser-deploy.

Database snapshot: 13.11.2026 · package version 5dc4410c54f8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90devopser-setup
    Expert guidance for scaffolding the DevOpser self-evolving software template locally — from git clone to an authenticated admin session at localhost:8000. Covers Bedrock Express provider selection (Bedrock, OpenAI, Anthropic), MFA-protected AWS credentials, and the four-check…
  • 100aws-ecs-fargate
    Deploy containers on ECS and Fargate. Configure task definitions, services, and load balancing. Use when running containerized workloads on AWS.
  • 100aws-ecs-fargate
    Deploy containers on ECS and Fargate. Configure task definitions, services, and load balancing. Use when running containerized workloads on AWS.
  • 100aws-ecs-fargate
    Deploy containers on ECS and Fargate. Configure task definitions, services, and load balancing. Use when running containerized workloads on AWS.
  • 100aws-ecs-fargate-container-service
    Use this skill when running serverless containerized applications on AWS using Amazon ECS and AWS Fargate task definitions.
  • 90devopser-customize
    Expert guidance for turning the DevOpser self-evolving software template into a real product. Covers the two chat surfaces (stateless `/` preview vs stateful `/chat`), the publicPaths route-visibility rule, adding a fourth LLM provider, and productization patterns from DevOpser…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.