Race Course Designer: Settings and maintenance
Operational reference for settings and maintenance in Race Course Designer.
Settings and maintenance
Code installs at ~/.local/share/gameaction360-race-course-designer. Private settings, controller lock, logs and browser profile live at ~/.ga360-race-course-designer outside package-owned code. Preferences disable password saving/autofill; the private browser profile can retain the normal authenticated Hub session. Use Sign out in the app on a shared station. An unreadable settings file is preserved and requires administrator review before launch.
Close Designer before update/uninstall. Workstation knows the install location and verifies package identity/checksums. A separate Updates launcher accepts a downloaded Designer ZIP and its SHA-256, and supports code rollback after an update. Settings/browser sessions remain. This initial release has no previous Designer release; other applications keep their independent versions. Removal retains private data and dependencies. No local web server, fixed port, external daemon or scheduler is introduced.
python3 app.py --desktop opens a normal application window; python3 app.py --kiosk or bash ./launch-kiosk.sh opens fullscreen. Workstation's existing platform/window adapter controls shared kiosk switching. Native desktop rendering and live Hub operation must be verified on the target desktop. Automated checks cover private settings, browser lifecycle, launcher/install behavior and the existing mapper geometry controls; Rails request tests are included in the Hub but require its Ruby/Rails environment.
Need more help with this?
Search a specific symptom, review related guides below, or prepare a report with the app version, operating system and exact error. Guides describe the documented release; installed versions and subscription access can differ.
Prepare a support report