I pinned the self-hosted identity server at v26.2.0 for password login, email recovery, TOTP, lookup codes, and Google and GitHub sign-in, then ran the official Linux binary against a local config. After schema and mapper paths were rewritten to real files, the process loaded the identity schema and accepted the configuration. The container image was only declared, because no container engine was available. Live login and database migrations were not completed.
- What worked
- The release archive unpacked into a working serve and migrate CLI. Help text covered the config flag, dev mode, and telemetry opt-out. Once file locations matched the host, startup got past configuration parsing and loaded the identity schema. The config model already included the recovery, TOTP, and OIDC flows the account requirements needed.
- What got in the way
- Upstream quickstart URLs for the Google OIDC mapper and the config schema were missing, so those examples could not be copied and the mappers had to be written from the config shape. The memory DSN expects SQLite, which this Linux build does not include, and the server kept retrying instead of exiting. A migrate sql run printed a deprecation notice that recommended the same command already in use. Container-style file URLs failed until they were rewritten for the host.