Deploy the new register.py to the server (copy button is not live yet)

[dhigby]

The branded token page, the Copy button and the link back to the instructions site are all in main (d7636dd) but the California server is still running the old register.py. Until it is redeployed, someone following the new site through step 1 lands on the old bare token page — which has no copy button and links to github.com, the exact thing we just moved people away from.

Follow server/SETUP.md as usual, plus one new setting:

# /etc/langtechdepot/register.env
SITE_URL=https://sillsdev.github.io/langtechdepot

Without it the service falls back to that same default, so the deploy is not broken if it is forgotten — but it is the one line to change when the site moves to its own name (#13).

Then check:

• https://depot.langtech.cloud/ shows the restyled form
• https://depot.langtech.cloud/signup?os=windows shows the same form (a second address for it, reserved for after the merge — the site links to /)
• a real registration shows the token with a working Copy button
• the Next: download the installer button lands on windows.html, not index.html
• the token email carries the instructions link

python3 server/test_register.py covers all of this against a stub Syncthing and passes 25/25, so a failure here is an environment problem rather than a code one.

[dhigby]

Handoff — @JimH44, this one is the blocker.

State as of tonight, all pushed to main:

• The instructions site is live and working: https://sillsdev.github.io/langtechdepot/ — four graphical steps, Windows and Linux, plus a help page. It rebuilds and redeploys itself on every push to main.
• The Windows download is one zip built by CI, and it checks out: https://sillsdev.github.io/langtechdepot/downloads/langtechdepot-windows.zip (CRLF line endings survive the trip).
• Step 1 links to https://depot.langtech.cloud/?os=windows, which returns 200 against the server as it is now. The site does not depend on this issue being done.

What is not done: the server still runs the old register.py. So right now a user who follows step 1 gets the old bare token page — no Copy button, no link back to step 2, and it still points at github.com. Everything in this issue's checklist is waiting on that one deploy. python3 server/test_register.py passes 25/25 against a stub, so a failure on the box is environment, not code.

Two things to know before deploying:

1. Add SITE_URL=https://sillsdev.github.io/langtechdepot to /etc/langtechdepot/register.env. If you forget it the code falls back to the same value, so the deploy is not broken — it is just the one line to change if the site ever moves (Users still see a github.io URL: pick a langtech.cloud name for the instructions site #13).
2. The token is now shown on the confirmation page as well as emailed, where before it was only emailed. Deliberate: a field user on a slow link who has to go find a mail client mid-install is one who does not finish. If you disagree, it is a small change in token_page().

Everything else is broken out: #13 (get the github.io name out of the URL), #14 (merge the two sites onto one host), #15 (a support address that reaches a person), #16 (the folder names in the step-4 picture are invented — they need checking against the real catalogue), #17 (Mac users get no answer), #18 (field-test the new one-zip Windows path).

Of those, #16 is the one that will embarrass us fastest if it is wrong, since the picture is teaching people what to look for in Syncthing.

[JimH44]

The new register.py has been put in place, and the webpage method of getting the Windows installer now works :-) Well done!

[dhigby]

Server-side status, now that register.env and the journal are readable.

Confirmed working, as @JimH44 reported:

• https://depot.langtech.cloud/ shows the restyled form
• https://depot.langtech.cloud/signup?os=windows shows the same form — returns 200
• a real registration shows the token with a working Copy button
• the Next: download the installer button lands on windows.html

The last checkbox cannot pass as written:

• the token email carries the instructions link — SMTP_HOST is empty, so [boot] logs smtp=no and no token email has ever been sent. The link is in the body (register.py:257), but nothing sends it.

That is worth a decision rather than a tick. The confirmation page is currently the only delivery, which inverts what CLAUDE.md describes:

The token is now shown on the confirmation page as well as emailed ... the mail copy is the backup, not the delivery.

There is no backup. A user who loses the page before pasting the token has no way to recover it and must register again. It also means ltd-sync-admin approve cannot notify anyone, so the non-auto-approve path is effectively unusable — though AUTO_APPROVE=true is set, so that path is not in use today.

Also: SITE_URL is not set in /etc/langtechdepot/register.env. Exactly as this issue predicted, nothing is broken — the code falls back to the same string — but it is the one line to change for #13.

For the record, the journal shows only one device has ever registered:

Sep 09 00:46  [register] JimHe-JIMH_WIN11 KS24TN4-... -> 2 folder(s)
Sep 10 04:52  [register] JimHe-JIMH_WIN11 KS24TN4-... -> 5 folder(s)
Sep 10 06:36  [register] JimHe-JIMH_WIN11 KS24TN4-... -> 6 folder(s)

Same device three times, offered more folders each time as the catalog grew — which is the catalog reaching an existing device working as designed. But it means #18 is genuinely untested: no machine other than Jim's has been through this.

Suggest closing this issue once the SMTP question is answered, and tracking the mail gap separately if it is not going to be configured now.