From 54d921a2a2243dded621b19399a3af53cf11f633 Mon Sep 17 00:00:00 2001
From: kisfenyo <nagyfenyvesi.viktor@gmail.com>
Date: Thu, 8 Jan 2026 17:25:58 +0100
Subject: [PATCH] removed comments

---
 booking-system/booking.yaml | 24 +-----------------------
 1 file changed, 1 insertion(+), 23 deletions(-)

diff --git a/booking-system/booking.yaml b/booking-system/booking.yaml
index 5ae0364..c95d4a3 100644
--- a/booking-system/booking.yaml
+++ b/booking-system/booking.yaml
@@ -11,7 +11,6 @@
 # - Multiple event types
 # - Booking notes
 # - White-label capable
-# - OIDC/SAML SSO support (Authentik integration!)
 #
 # Prerequisites:
 # 1. Create databases in shared PostgreSQL:
@@ -24,32 +23,11 @@
 #    \c calcom
 #    GRANT ALL ON SCHEMA public TO calcom;
 #
-#    -- SSO/SAML database (required for OIDC!)
-#    CREATE DATABASE calcom_saml;
-#    GRANT ALL PRIVILEGES ON DATABASE calcom_saml TO calcom;
-#    \c calcom_saml
-#    GRANT ALL ON SCHEMA public TO calcom;
-#
 # 2. Set up Stripe account at https://stripe.com (Hungary supported)
 #    Get API keys from Dashboard -> Developers -> API keys
 #
-# 3. Set up Authentik OIDC provider:
-#    - Create OAuth2/OpenID Provider in Authentik
-#    - Client type: Confidential
-#    - Redirect URIs: https://booking.dooplex.hu/api/auth/callback/oidc
-#    - Note the Client ID, Client Secret
-#    - Well-known URL: https://authentik.dooplex.hu/application/o/<slug>/.well-known/openid-configuration
-#
-# 4. (Optional) Set up Google OAuth for calendar sync:
+# 3. (Optional) Set up Google OAuth for calendar sync:
 #    https://console.cloud.google.com/apis/credentials
-#
-# After deployment:
-# 1. Access https://booking.dooplex.hu
-# 2. Create first user with email matching SAML_ADMINS
-# 3. Go to Settings → Security → SSO
-# 4. Click "Configure SSO with OIDC"
-# 5. Enter Client ID, Client Secret, Well-known URL from Authentik
-# 6. Configure event types, availability, and Stripe integration
 ---
 apiVersion: v1
 kind: Namespace