Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Offer a way back to Setup from the lobby

Offen
  • Stimmt etwas nicht?
#513 4 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@Patriciaath999 arbeitet bereits daran.

Seit 26.10.2026.

  • #528 von @YEH-YU-YANG — offen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

After the first Setup, neither the web server nor the desktop app offers any way back to the Setup page. Someone who skipped the Google API key there, which the page marked Optional, starts interviews in which the interviewer never speaks, and the only fix is to find codetrial.env.local, edit it by hand and restart. On the desktop app that file sits in %LOCALAPPDATA%\org.sysprog21.codetrial, which nothing in the app names.

I propose adding a way back to Setup from the lobby, as one change covering both the web server and the desktop app, since the desktop app only shows the server's pages.

Current behavior

Setup is a cold-start phase, not a route of the app. At ce2c50a, main serves it only when is_cold_start holds (src/main.rs:356, src/main.rs:538): no --config, no primary config file, and no LIVEKIT_* in the environment. serve_setup (src/main.rs:569) runs setup_service (src/web/setup.rs:45) on its own router until the config is written, then hands the socket to the full app, which has no Setup route. Once the file exists, every later launch skips Setup.

Proposed behavior

A "Change keys" entry in the lobby opens a Setup page prefilled with the current LiveKit URL and the presence of each key, never the secret values. Saving writes the same codetrial.env.local through the existing validation and credential probe, then the server restarts, or the desktop app restarts its child server, so the new keys take effect.

Setup's existing guard applies unchanged: the page answers only to a loopback Host (src/web/setup.rs:73), so a server deployed for other people never shows the entry and stays configured through its file.

Decision needed

How the new keys take effect:

  1. Restart the process after writing. Simplest, and the startup path stays the only place keys are read. On the web server this needs a supervisor or the user to start it again; the desktop app can restart its child itself.
  2. Reload the config in the running server. No restart, but the provider pool (src/main.rs:487) and the decision to host interviewers (src/main.rs:450) are made once at startup today, so this touches far more code.

I would start with option 1. Which one should this take?

Vorherrschende Sprache
Rust
Sterne
215
Forks
141
Ø Merge
1 T. 12 Std.
Gemergte PRs (30 T.)
232

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus sysprog21/codetrial

Alle Issues in sysprog21/codetrial

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.