What problem does it solve? Deploying R Shiny or Python web applications to production at FGCZ requires coordinating Docker images, ShinyProxy YAML configuration, LDAP authentication, and volume mounts, and mistakes in any of these cause failed deployments or broken access control. ## Core Features & Use Cases - Guided deployment workflows: Step-by-step procedures for deploying apps using the fgcz_base_image or building custom Docker images, including local testing before production release. - LDAP access control: Ready-to-use R code patterns for restricting data access based on B-Fabric user roles (R_2 employees vs R_3 external users) and project membership. - Python app support: Documented fixes for production gotchas when deploying Gradio, Streamlit, or FastAPI apps, including venv paths, SCIPY_ARRAY_API, and root_path proxying. - Use Case: A bioinformatician finishes a Seurat-based Xenium explorer app and needs it live at shiny.fgcz.uzh.ch with project-level access restrictions; this skill walks them through configuration, testing, and service restart. ## Quick Start Ask the agent to deploy your Shiny app to FGCZ ShinyProxy using the fgcz_base_image and it will generate the configuration, Dockerfile, and restart commands.