admin-deploy

What it does and when to use it

Use when deploying this admin project to a server or updating a server to a new commit.

How it works

SKILL.md has no level-two headings · 17 lines, 195 words

---
name: admin-deploy
description: "Use when deploying this admin project to a server or updating a server to a new commit."
---

# Deploy / update a server

```bash
git pull && composer install --no-dev -o && npm ci && npm run build
php artisan migrate --force && php artisan permissions:sync && php artisan optimize
php artisan storage:link   # first deploy only: public/storage for the Settings branding files
php artisan admin:doctor
sudo supervisorctl restart all
```

- `composer install` gets `yuanmaharsyah/admin-core` from Packagist. A private fork over SSH needs a read-only deploy key on the server (`vendor/yuanmaharsyah/admin-core/README.md` → Private forks over SSH).
- Production: `APP_DEBUG=false`, a real queue driver with a supervised worker, the scheduler in cron (`php artisan schedule:run` every minute), `ADMIN_SEED_PASSWORD` set before the first seed, or no seeder and `php artisan admin:create-superadmin`.
- `php artisan admin:doctor` checks the npm dependencies, the module cache, the storage link and the environment.
- Public pages can be closed during maintenance with `php artisan admin:access maintenance --message="..."` and reopened with `php artisan admin:access open`.
- PHP down (deploy restart, crashed FPM): the web server answers itself, so point it at the static page in the server block, `error_page 502 504 /errors/502.html;` (the file is `public/errors/502.html`, styled like the app's error pages). Laravel renders every other error page itself.

Versions

The database has no other skills named admin-deploy.

Database snapshot: 13.11.2026 · package version 24efc4451fc1 (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

• 90admin-interface-security
  Secure the administrative interface of model registries. Use when building, deploying, or reviewing model registry access controls and admin interfaces.
• 90admin-ui-components
  Use before building or changing any admin screen or UI component: the catalogue of house-style components (shadcnspace-inspired), what each is for, and how to use it.
• 100bdb-deploy
  Use when the user wants to build and deploy a project to a real server via rsync over SSH — "deploy this", "push the build live", "sync to production". Not for git push/PR workflows, and not a replacement for a real CI pipeline; this is the direct-deploy path.
• 100new-page
  Use when building a brand-new admin panel page or screen from scratch in ANY web framework. Enforces design quality gates. Do NOT use for modifying existing pages — use ui-change instead.
• 95commit-push-deploy
  Commit, push, then deploy only if allowlisted infra already exists. Use for /commit-push-deploy, "commit push deploy", "deploy this". Must push. Never force-push. Never invent infra.
• 100headscale-deploy
  Deploy, configure, and maintain a self-hosted Headscale control server on Linux or Docker. Use when setting up a new Headscale instance, troubleshooting deployment issues, or configuring server settings.