deploying-public-apps

Automates deployment of public-facing apps with per-app manifests, DDNS, and Caddy routing.

2|Updated Dec 13, 2025

Search Tags:#kubernetes #deploy #auth #flux #caddy #public-apps #authelia

Ready to run

npx skills add https://github.com/saavy1/sb --skill deploying-public-apps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploying-public-apps
Source: https://github.com/saavy1/sb/tree/main/docs/.claude/skills/deploying-public-apps
Command: npx skills add https://github.com/saavy1/sb --skill deploying-public-apps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploys public-facing apps that handle their own authentication, removing the need for Authelia forward auth in many scenarios.

Core Features & Use Cases

Supports rapid deployment of apps like Jellyfin or Minecraft that manage their own authentication and domain routing.
Provides a structured workflow for creating per-app manifests, updating Flux kustomizations, and configuring DDNS and Caddy routes.
Facilitates end-to-end deployment including manifest creation, DNS and TLS provisioning, and post-deploy validation.

Quick Start

Create the app manifests, wire them into Flux, configure the domain in DDNS, add a Caddy route with no forward_auth, and push to trigger reconciliation and deployment.

Frequently Asked Questions about deploying-public-apps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I deploy public apps with Kubernetes without Authelia forward auth?▼

Deploy public apps handling their own authentication by creating per-app manifests, configuring Flux kustomizations, and setting up Caddy routes without forward_auth dependencies. This automates DNS provisioning and deployment for services like Jellyfin or Minecraft.

Can I use Caddy and Flux to route public Kubernetes apps that manage their own login?▼

Yes, Caddy and Flux route public Kubernetes apps managing their own login. You create per-app manifests, wire them into Flux kustomizations, and add Caddy routes without forward_auth, triggering reconciliation for end-to-end deployment.

What's the best way to expose Jellyfin or Minecraft publicly on Kubernetes?▼

Expose Jellyfin or Minecraft publicly by creating per-app Kubernetes manifests, updating Flux kustomizations, configuring DDNS domains, and adding Caddy routes. This handles TLS provisioning and post-deploy validation without requiring Authelia forward auth.

Do I need Authelia forward auth to publish public-facing apps on Kubernetes?▼

No, Authelia forward auth is not needed for public-facing apps that handle their own authentication. You can deploy services like Jellyfin by creating manifests, configuring Flux, and routing domains via Caddy without forward_auth dependencies.

How does Flux-based deployment work for public apps with built-in auth?▼

Flux-based deployment works by wiring per-app manifests into Flux kustomizations and pushing to trigger reconciliation. This automates the end-to-end process including manifest creation, DDNS configuration, Caddy routing, and post-deploy validation for self-authenticating apps.

What are the limitations of deploying public apps without forward auth?▼

Deploying public apps without forward auth requires the applications to handle their own authentication securely. This approach applies to services like Jellyfin and Minecraft but is not suitable for apps lacking built-in authentication mechanisms.