Skip to content

Commit a53bac2

Browse files
committed
Clarify admin user setup in DEPLOY.md
Explain GitHub handle vs email/password for system user claim.
1 parent d6f6f86 commit a53bac2

1 file changed

Lines changed: 19 additions & 3 deletions

File tree

DEPLOY.md

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,11 +19,27 @@ ow infra migrate run
1919

2020
### 3. Claim the system user
2121

22-
The system user (`00000000-...`) owns shared resources (the API database config, etc.). Claim it with your username:
22+
The system user (`00000000-...`) owns shared resources (the API database config, etc.). Claim it with your admin identity.
23+
24+
**The username must match exactly how you will log in:**
25+
26+
- **GitHub OAuth** → use your GitHub username (e.g. `max-lt`)
27+
- **Email/password (headless)** → use your email (e.g. `admin@example.com`)
28+
29+
> **Important:** Anyone who signs up or logs in with this username gets admin access to platform resources. Double-check it before proceeding.
30+
31+
```bash
32+
# GitHub login
33+
ow infra users create my-github-handle --system
34+
35+
# Or email/password login (headless, no GitHub)
36+
ow infra users create admin@example.com --system --password
37+
```
38+
39+
Update the alias to reference the admin user:
2340

2441
```bash
25-
ow infra users create your-username --system
26-
ow alias set infra --db postgres://... --user your-username --force
42+
ow alias set infra --db postgres://... --user my-github-handle --force
2743
```
2844

2945
### 4. Configure platform storage

0 commit comments

Comments
 (0)