deploy-to-connect
FeaturedDeploy or publish Python and R content to a Posit Connect server using rsconnect-python or the R rsconnect package. Handles interactive apps and dashboards, web APIs, rendered documents, and prepared bundles/manifests. Use whenever the user asks to deploy, publish, or redeploy content to Posit Connect, or mentions rsconnect. Consult this skill instead of guessing flags or commands.
Install
Quality Score: 92/100
Skill Content
Details
- Author
- posit-dev
- Repository
- posit-dev/skills
- Created
- 9 months ago
- Last Updated
- yesterday
- Language
- R
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
deploy-to-railway
Use when deploying a project to Railway from scratch — provisioning a Postgres database, one or more app services (a full-stack monolith OR separate frontend/backend), an S3-compatible bucket, sharing credentials + env vars between services, wiring GitHub auto-deploy on merge to main, and adding auth (Google SSO or Cloudflare Zero Trust in front). Triggers on "deploy this to Railway", "get it live on Railway", "set up Railway with a database + auto deploy", "split front/back end services on Railway", "add an S3 bucket on Railway", "share env vars between Railway services". Carries the hard-won gotchas (NIXPACKS Node version, npm-version lockfile skew, RLS-safe DATABASE_URL, DB-role password rotation, GitHub App authorization) that turn a 6-hour debug into a 20-minute deploy.
deploy
Deploy a managed project to production, executed strictly from that project's structured deploy playbook — confirm-gated, never improvised. Use when the user says "deploy", "deploy <project>", "ship <project> to prod", "run the deploy", or "push <project> live". Reads the project's context.md + the deploy playbook it points to (e.g. a repo README "Deploy" section), presents the full ordered plan, then runs it one step at a time, pausing before each production-mutating step.
deploy
Configure and run the LOCAL deploy — install the app on this machine or start its dev server — verifying it succeeds