From 470f3a698063be1a8d519e9be6d771d15c8d2774 Mon Sep 17 00:00:00 2001 From: Keysat Date: Wed, 17 Jun 2026 15:41:15 -0500 Subject: [PATCH] Resequence install steps so the admin UI opens before operator-name and BTCPay --- install.html | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/install.html b/install.html index 37d04f8..9273ca4 100644 --- a/install.html +++ b/install.html @@ -78,11 +78,24 @@

BTCPay Server is declared as a required dependency. If you don’t have it installed yet, StartOS will prompt you to install it as part of the same flow.

-

Step 2: Set your operator name

-

Open the admin web UI (Step 5) and go to Settings. Set your operator name there: a short label that identifies you as the seller, e.g. "aurora-software", "northpath", "my-name". This shows up on the public purchase pages and in the audit log.

+

Step 2: Get your admin API key

+

On Keysat’s StartOS service page, go to Actions → Show credentials. This reveals the 64-hex-character admin API key that gates all /v1/admin/* endpoints, including the admin UI.

+ +
+ +

Treat this key like a password. Anyone with it can issue, revoke, or read every license you’ve ever sold. Don’t paste it into Slack. Don’t check it into Git.

+
+ +

Step 3: Open the admin UI

+

Click the Launch UI button on Keysat’s service page. (StartOS surfaces this for any service that defines a type: 'ui' interface.) Paste the admin key from the previous step into the sign-in form.

+ +

From here on, you work in the admin UI. The StartOS Actions tab is reserved for the few operations that must happen outside the web UI: showing credentials, setting the web UI password, and activating or checking the Keysat self-license.

+ +

Step 4: Set your operator name

+

In the admin UI, go to Settings. Set your operator name there: a short label that identifies you as the seller, e.g. "aurora-software", "northpath", "my-name". This shows up on the public purchase pages and in the audit log.

This change is live-reloaded; you don’t need to restart the service.

-

Step 3: Connect BTCPay

+

Step 5: Connect BTCPay

Make sure BTCPay Server is running and has at least one store with a configured payment method (on-chain wallet or Lightning node). Without a payment method, BTCPay will reject Keysat’s invoice creation.

In the admin web UI, go to Settings → Payment providers and click Connect BTCPay (agents can drive the same connect over the API with POST /v1/admin/btcpay/connect). You’ll be redirected to BTCPay’s authorize page, where you grant Keysat the permissions it needs:

@@ -119,19 +132,6 @@ payment_methods: [BTC-OnChain, BTC-LightningNetwork]If payment_methods is empty, head back to BTCPay and configure at least one before continuing.

-

Step 4: Get your admin API key

-

Go to Actions → Show credentials. This reveals the 64-hex-character admin API key that gates all /v1/admin/* endpoints, including the admin UI.

- -
- -

Treat this key like a password. Anyone with it can issue, revoke, or read every license you’ve ever sold. Don’t paste it into Slack. Don’t check it into Git.

-
- -

Step 5: Open the admin UI

-

Click the Launch UI button on Keysat’s service page. (StartOS surfaces this for any service that defines a type: 'ui' interface.) Paste the admin key from the previous step into the sign-in form.

- -

From here on, you work in the admin UI. The StartOS Actions tab is reserved for the few operations that must happen outside the web UI: showing credentials, setting the web UI password, and activating or checking the Keysat self-license.

-

Step 6: Define your first product

In the admin UI, go to Products → Create a new product and fill in:

@@ -185,10 +185,10 @@ payment_methods: [BTC-OnChain, BTC-LightningNetwork]On this page Prerequisites 1. Install Keysat - 2. Set operator name - 3. Connect BTCPay - 4. Get admin key - 5. Open the admin UI + 2. Get admin key + 3. Open the admin UI + 4. Set operator name + 5. Connect BTCPay 6. First product 7. Default policy 8. Purchase URL