npx claudepluginhub pjt222/agent-almanacThis skill uses the workspace's default tool permissions.
---
Deploys ShinyProxy to host multiple containerized Shiny apps with per-app authentication, access control, usage tracking, and scaling via Docker. For multi-app Shiny hosting beyond single deployments.
Deploys apps to Render by analyzing codebases, generating render.yaml blueprints, and providing dashboard deeplinks. For Git-backed services, Docker images, databases, and cron jobs.
Deploys Git-backed apps to Render by analyzing codebases, generating render.yaml blueprints, creating services via MCP, and providing dashboard deeplinks. Use for hosting on Render.
Share bugs, ideas, or general feedback.
Deploy a Shiny application to shinyapps.io, Posit Connect, or a Docker container.
Ensure the app is self-contained and deployable:
# Check for missing dependencies
rsconnect::appDependencies("path/to/app")
# For golem apps, ensure DESCRIPTION lists all Imports
devtools::check()
# Verify the app runs cleanly
shiny::runApp("path/to/app")
Verify these files exist:
app.R (or ui.R + server.R)renv.lock (recommended for reproducible deployments).Rprofile does NOT call mcptools::mcp_session() in productionExpected: App runs locally without errors and all dependencies are captured.
On failure: If appDependencies() reports missing packages, install them and update renv.lock. If the app uses system libraries (e.g., gdal, curl), note them for the Docker path.
# One-time account setup
rsconnect::setAccountInfo(
name = "your-account",
token = Sys.getenv("SHINYAPPS_TOKEN"),
secret = Sys.getenv("SHINYAPPS_SECRET")
)
# Deploy
rsconnect::deployApp(
appDir = "path/to/app",
appName = "my-app",
appTitle = "My Application",
account = "your-account",
forceUpdate = TRUE
)
Store credentials in .Renviron (never in code):
# .Renviron
SHINYAPPS_TOKEN=your_token_here
SHINYAPPS_SECRET=your_secret_here
Expected: App deployed and accessible at https://your-account.shinyapps.io/my-app/.
On failure: If authentication fails, regenerate tokens at shinyapps.io dashboard > Account > Tokens. If package installation fails on the server, check that all packages are available on CRAN — shinyapps.io cannot install from GitHub by default.
# Register server (one-time)
rsconnect::addServer(
url = "https://connect.example.com",
name = "production"
)
# Authenticate (one-time)
rsconnect::connectApiUser(
account = "your-username",
server = "production",
apiKey = Sys.getenv("CONNECT_API_KEY")
)
# Deploy
rsconnect::deployApp(
appDir = "path/to/app",
appName = "my-app",
server = "production",
account = "your-username"
)
Expected: App deployed and accessible on the Posit Connect instance.
On failure: If the server rejects the connection, verify the API key and server URL. If packages fail to install, check that Connect has access to the required repositories (CRAN, internal CRAN-like repos).
Create a Dockerfile:
FROM rocker/shiny-verse:4.4.0
# Install system dependencies
RUN apt-get update && apt-get install -y \
libcurl4-openssl-dev \
libssl-dev \
libxml2-dev \
&& rm -rf /var/lib/apt/lists/*
# Install R packages
RUN R -e "install.packages(c('shiny', 'bslib', 'DT', 'plotly'))"
# Copy app
COPY . /srv/shiny-server/myapp/
# Configure Shiny Server
COPY shiny-server.conf /etc/shiny-server/shiny-server.conf
# Expose port
EXPOSE 3838
# Run
CMD ["/usr/bin/shiny-server"]
Create shiny-server.conf:
run_as shiny;
server {
listen 3838;
location / {
site_dir /srv/shiny-server/myapp;
log_dir /var/log/shiny-server;
directory_index on;
}
}
Build and run:
docker build -t myapp:latest .
docker run -p 3838:3838 myapp:latest
Expected: App accessible at http://localhost:3838.
On failure: If the build fails on package installation, add missing system libraries to the apt-get install line. If the app doesn't load, check Shiny Server logs: docker exec <container> cat /var/log/shiny-server/*.log.
# Check the deployed URL responds
response <- httr::GET("https://your-app-url/")
httr::status_code(response) # Should be 200
# For Docker
response <- httr::GET("http://localhost:3838/")
httr::status_code(response)
Manual verification checklist:
Expected: App responds with HTTP 200 and all features work.
On failure: Check server logs for the specific deployment platform. Common issues: environment variables not set in production, database connections using localhost instead of production URLs, or file paths that only exist locally.
Monitor via the dashboard at https://www.shinyapps.io/admin/#/applications.
# Check deployment status via API
connectapi::connect(
server = "https://connect.example.com",
api_key = Sys.getenv("CONNECT_API_KEY")
)
Add health check to Dockerfile:
HEALTHCHECK --interval=30s --timeout=10s --retries=3 \
CMD curl -f http://localhost:3838/ || exit 1
Expected: Monitoring configured for the deployment target.
On failure: If health checks fail intermittently, increase timeout values. Shiny apps can be slow to respond during initial load.
.Renviron or CI secrets, not in codesystem.file() (for package data) or environment variables (for external resources)..Rprofile that loads mcptools::mcp_session() or devtools. Use conditional loading or separate profiles.apt-get install.remotes package and explicit installation in the deployment.scaffold-shiny-app — create app structure before deploymentcreate-r-dockerfile — detailed Docker configuration for R projectssetup-docker-compose — multi-container setups for Shiny with databasessetup-github-actions-ci — CI/CD including automated deploymentoptimize-shiny-performance — performance tuning before deploying to production