Run any Skill in Manus with one click

streamlit-private-deploy

Stars0

Forks0

UpdatedJune 5, 2026 at 01:12

Deploy a streamlit-private project to a managed host (Railway first; Render/Fly.io later) and return the private, authenticated URL. Use when the user wants to "deploy my Streamlit app", "ship it", "put it online privately", or "deploy to Railway".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

DecisionNerd

DecisionNerd/streamlit-private

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	streamlit-private-deploy
description	Deploy a streamlit-private project to a managed host (Railway first; Render/Fly.io later) and return the private, authenticated URL. Use when the user wants to "deploy my Streamlit app", "ship it", "put it online privately", or "deploy to Railway".

streamlit-private: deploy

Deploy the gateway-fronted Streamlit app to the managed host recorded in the manifest by running the streamlit-private CLI, then report the private URL.

When to use

The repo is initialized (streamlit-private.yaml exists) and the user wants it live.
The user says "deploy", "ship it", "deploy to Railway", or "give me a private URL".

If the repo is not yet initialized, run the streamlit-private-init skill first.

Prerequisites

For Railway, the railway CLI must be installed and authenticated (railway login, or a RAILWAY_TOKEN environment variable for headless/CI use). deploy checks this first and prints guidance if it's missing — surface that to the user rather than working around it.

Hard rules

Read providers from the manifest. The hosting provider is recorded in streamlit-private.yaml; deploy to that host. Do not invent infrastructure or deploy by hand outside the CLI.
Do not reimplement the CLI. Run streamlit-private deploy; do not script raw host API calls yourself.
Provider secrets (auth + hosting) must be set as environment variables. Never commit secrets or paste them into files.

Steps

Confirm streamlit-private.yaml exists. If not, switch to streamlit-private-init.
Determine the hosting provider from the manifest (e.g. railway).
Ensure required secrets are configured (see .env.example); if any are missing, ask the user to set them on the host rather than guessing values.
Run:
```
uvx streamlit-private deploy railway
```
(substitute the manifest's hosting provider for railway).
Report the returned private URL to the user, and explain the access model:
- unauthenticated visitors are sent to Sign In,
- authenticated non-members can Request Access,
- authenticated organization members are let straight through.
If the deploy fails, switch to the streamlit-private-troubleshoot skill.

Notes

The deploy ships two things behind one URL: the auth gateway and the unmodified Streamlit app. Streamlit's WebSockets are proxied by the gateway — interactivity should work normally.
To invite users or approve access requests after deploying, use the streamlit-private-invite and streamlit-private-access-requests skills.

More from this repository

same repository

streamlit-private-access-requests

DecisionNerd/streamlit-private

List and act on pending access requests for a privately deployed Streamlit app — approve (add the user to the organization) or reject them via streamlit-private. Use when the user (an admin) wants to "approve access requests", "see who's requested access", or "let someone in".

2026-06-040

streamlit-private-configure

DecisionNerd/streamlit-private

Reconfigure an existing streamlit-private project — switch the auth provider (e.g. Clerk → WorkOS) or hosting provider (e.g. Railway → Render), or regenerate deployment assets, while preserving the user's application code. Use when the user wants to "change auth provider", "switch hosting", or "regenerate my streamlit-private config".

2026-06-040

streamlit-private-init

DecisionNerd/streamlit-private

Initialize a Streamlit app for private deployment with streamlit-private — scaffold a new app or wrap an existing Streamlit repo, adding a gateway, deployment assets, and a manifest without touching application code. Use when the user wants to "make my Streamlit app private", "set up streamlit-private", or "add auth to my Streamlit app".

2026-06-040

streamlit-private-invite

DecisionNerd/streamlit-private

Invite a user to a privately deployed Streamlit app's organization via streamlit-private, so they become a member and gain access. Use when the user (an admin) wants to "invite someone", "add a user", or "give my colleague access" to the app.

2026-06-040

streamlit-private-troubleshoot

DecisionNerd/streamlit-private

Diagnose a failed streamlit-private deployment or broken private access — missing provider secrets, proxy/WebSocket issues, auth/membership problems, or a misconfigured manifest. Use when the user says "my deploy failed", "the app won't load", "sign-in is broken", or "the page is blank / keeps reconnecting".

2026-06-040

name	streamlit-private-deploy
description	Deploy a streamlit-private project to a managed host (Railway first; Render/Fly.io later) and return the private, authenticated URL. Use when the user wants to "deploy my Streamlit app", "ship it", "put it online privately", or "deploy to Railway".

streamlit-private: deploy

Deploy the gateway-fronted Streamlit app to the managed host recorded in the manifest by running the streamlit-private CLI, then report the private URL.

When to use

The repo is initialized (streamlit-private.yaml exists) and the user wants it live.
The user says "deploy", "ship it", "deploy to Railway", or "give me a private URL".

If the repo is not yet initialized, run the streamlit-private-init skill first.

Prerequisites

For Railway, the railway CLI must be installed and authenticated (railway login, or a RAILWAY_TOKEN environment variable for headless/CI use). deploy checks this first and prints guidance if it's missing — surface that to the user rather than working around it.

Hard rules

Read providers from the manifest. The hosting provider is recorded in streamlit-private.yaml; deploy to that host. Do not invent infrastructure or deploy by hand outside the CLI.
Do not reimplement the CLI. Run streamlit-private deploy; do not script raw host API calls yourself.
Provider secrets (auth + hosting) must be set as environment variables. Never commit secrets or paste them into files.

Steps

Confirm streamlit-private.yaml exists. If not, switch to streamlit-private-init.
Determine the hosting provider from the manifest (e.g. railway).
Ensure required secrets are configured (see .env.example); if any are missing, ask the user to set them on the host rather than guessing values.
Run:
```
uvx streamlit-private deploy railway
```
(substitute the manifest's hosting provider for railway).
Report the returned private URL to the user, and explain the access model:
- unauthenticated visitors are sent to Sign In,
- authenticated non-members can Request Access,
- authenticated organization members are let straight through.
If the deploy fails, switch to the streamlit-private-troubleshoot skill.

Notes

The deploy ships two things behind one URL: the auth gateway and the unmodified Streamlit app. Streamlit's WebSockets are proxied by the gateway — interactivity should work normally.
To invite users or approve access requests after deploying, use the streamlit-private-invite and streamlit-private-access-requests skills.