Beta tester checklist

Ten things to try, in order. For each one, note whether it matched the expected result. Report anything that did not by email to beta@getportdeck.com (see the beta guide). Never send secrets.

1. Install

• Do: run the install command from the beta guide on a clean server.
• Expect: the installer finishes, prints the web and ops console addresses and says the stack is healthy.
• Report: the version, the install mode, how long it took, any error, and any question that was unclear.

2. Sign in and secure the admin account

• Do: open the ops console, sign in as admin, enrol two-factor, change the password, delete first-admin-password.txt.
• Expect: you get in only after a two-factor code. The new password works.
• Report: any step where the instructions did not match what you saw.

3. Run the first-run wizard

• Do: go through all six steps. Skip one on purpose, then finish it from its own page later.
• Expect: each step saves and checks its work. A skipped step can be done later. After finishing, the wizard's address (/setup on your Portdeck web address) answers 404.
• Report: a step that failed, confused you, or let you do something unsafe.

4. Activate your beta key

• Do: paste your beta key on the Licenses page and click Check key. Read the beta agreement in the preview. Try Activate this key without ticking the box. Then tick "I have read the beta agreement above and accept it" and activate.
• Expect: the preview shows the plan, limits and dates and the agreement. Without the tick, activation is blocked and the key is not in use. After you tick and activate, the key is listed under Beta keys as accepted, with plan Enterprise and an expiry 90 days after issue.
• Report: a message that was wrong or unclear, wrong dates or plan, no agreement shown, or the key taking effect before you accepted.

5. Sign in as the workspace owner and invite someone

• Do: sign in at the web address with the owner account from the wizard. Change the temporary password and set up two-factor. Invite a second person and copy the invite link.
• Expect: the owner flow works. The invite link opens a sign-up for the invited person with the role you chose.
• Report: any dead end, and which role you picked.

6. Connect a second server

• Do: add a server, run the install command on a second machine.
• Expect: within a minute the server shows as connected with CPU, memory and disk filled in.
• Report: the server's OS and architecture, the exact point where it stopped, and whether the gateway address was reachable from the server.

7. Launch an app

• Do: launch nginx from the approved list with port 8080.
• Expect: the status becomes Running, Open app works, and the Logs tab shows output.
• Report: the image, the size, the host it landed on, and any wrong status.

8. Stop, start, restart and delete

• Do: stop the app, start it, restart it, then delete it.
• Expect: each action completes and the status follows. After delete the app is gone from the list.
• Report: an action that hung, failed, or left something behind (check docker ps on the server).

9. Give an app a public address

• Do: only if you used caddy-domain or caddy-private. Launch an app on the same machine as Portdeck. In its Access tab, choose Live and type a name. Create the DNS record as shown.
• Expect: the tab shows the record to create and a DNS check. Once the name reaches the machine, Caddy serves the app over HTTPS.
• Report: the mode, what the DNS check said, and whether HTTPS worked.

10. Upgrade Portdeck, then roll back

• Do: when we announce a newer beta version, run bin/upgrade.sh --version <NEW-VERSION> --dry-run, then the real upgrade. Afterwards run bin/upgrade.sh status. If asked and the schema did not change, try bin/upgrade.sh rollback --dry-run.
• Expect: the dry run lists what it will do and changes nothing. The real upgrade backs up first, ends healthy, and prints the old and new version. Your apps and accounts are still there.
• Report: the exit code, the old and new version, the output of bin/upgrade.sh status, and anything missing afterwards.