Deploy Jac servers to production with Kubernetes, databases, webhooks, and monitoring.
npx skills add https://github.com/PMN123/trapdoor --skill jac-sv-deploy-pmn123
Please help me install this Agent Skill. Skill: jac-sv-deploy Source: https://github.com/PMN123/trapdoor/tree/main/.agents/skills/jac-sv-deploy Command: npx skills add https://github.com/PMN123/trapdoor --skill jac-sv-deploy-pmn123
jac start and --scale deployments correctly. ## Core Features & Use Cases - Production server configuration: Covers jac start flags (--no-client, --faux, --profile prod), disabling Swagger docs, and choosing SQLite, MongoDB, or Redis backends with clear config precedence rules. - Kubernetes deployment: Documents jac start app.jac --scale, --dry-run validation, HPA autoscaling, TLS via cert-manager, jac scale status, and the destructive jac scale destroy. - External integrations: Explains webhook walkers with API-key plus HMAC-SHA256 auth, WebSocket walkers with broadcast, S3 file storage with presigned URLs, Prometheus metrics, and Redis distributed locks. - Use Case: You have a Jac app running locally on SQLite and need to ship it to a Kubernetes cluster with a custom domain, HTTPS, autoscaling, and a Stripe-style webhook callback. This Skill walks through the exact jac.toml blocks and commands, including the two-step TLS flow. ## Quick Start Ask the assistant to deploy your Jac app to Kubernetes with a custom domain, TLS, and autoscaling using the jac --scale workflow.High-intent search queries and answers about installing and using this skill.
Run jac start app.jac --scale to deploy source directly into the cluster on a PVC without building an image. Always run with --dry-run first to lint config and catch errors like bad resource units or invalid HPA bounds before the full deploy.
HTTPS is a two-step process: first deploy plain with --scale and point your domain's CNAME at the printed NLB hostname, then run jac start app.jac --scale --enable-tls. cert-manager with Let's Encrypt patches the live ingress without a redeploy.
No. Multi-replica deployments with SQLite cause corruption and confusion. Going past one replica requires setting MONGODB_URI for the database and REDIS_URL for the cache tier and distributed locks.
Webhook walkers use API-key plus HMAC auth, not JWT. Create a key via POST /api-key/create, then callers send X-API-Key and X-Webhook-Signature, which is an HMAC-SHA256 of the raw body keyed by the API key.
jac scale destroy deletes the entire Kubernetes namespace including persistent volumes, so all data is lost permanently. There is a y/N confirmation prompt but no undo, so back up data before running it.
Webhook walkers only answer on POST /webhook/<name>, not /walker/<name>, and regular walkers do the reverse. A 404 on the wrong path indicates a routing mismatch, not a registration failure.
nihalnihalaniWire main.jac entry modules, endpoints, and client-server imports for fullstack Jac applications.
snoodleboot-ioDesigns Grafana dashboards with hierarchical layouts, panel selection, and alerting annotations.
nihalnihalaniExplains Jac server-side authentication semantics for JWT, roles, and endpoint visibility.
haJ1tGenerates Dockerfiles, Kubernetes manifests, Helm charts, and service mesh configurations for containerized applications.