From d53699d0f82db9571c37e52f2f46325ecb3b905a Mon Sep 17 00:00:00 2001 From: Lakhan Samani Date: Fri, 14 Aug 2026 20:06:50 +0530 Subject: [PATCH] fix(site): getting-started still described v1 configuration MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Step 2 told users to "Configure environment variables from dashboard". v2 removed both halves of that: configuration is CLI-flags only (no .env, no OS env vars), and the dashboard cannot update server config at all. Following it, a user deploys, opens the dashboard, and finds nothing to configure — after the server has already refused to start without --url and --encryption-key. --- components/GettingStarted.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/GettingStarted.tsx b/components/GettingStarted.tsx index 54d2647..5c90d3f 100644 --- a/components/GettingStarted.tsx +++ b/components/GettingStarted.tsx @@ -10,7 +10,7 @@ const startingSteps = [ { label: "Setup instance", description: - "Open authorizer instance endpoint in browser. Sign up as an admin with a secure password. Configure environment variables from dashboard", + "Configure the server at startup: v2 takes all configuration as CLI flags — there is no .env file, and the dashboard can no longer change server config. --url, --client-id, --client-secret, --admin-secret, --jwt-* and --encryption-key are required. Then open the instance in your browser and sign in with your admin secret.", link: "https://docs.authorizer.dev/getting-started", }, {