Is it possible to skip the "Setup token" in the Setup Wizard?

[al-lac]

It would be great if there was a way to skip the Setup token somehow for UI based deployments. Even providing the token via a docker env var would be great. Or is there another way to skip it?

[rathlinus]

you dont need the token when setting up via env

[al-lac]

Ok great, what if I still want to provide some values in the UI like the mail server, but still skip the setup token. What would I need to set for this use case?

[rathlinus]

You set your password in env and then you can do it in the ui

[al-lac]

With env var would this be? This is my current config:

server:
  image: ghcr.io/bulwarkmail/webmail:1.7.3
  restart: on-failure
  environment:
    HOSTNAME: "0.0.0.0"
    PORT: "3000"
    APP_NAME: "Bulwark Webmail"
    APP_SHORT_NAME: "Webmail"
    APP_DESCRIPTION: "Modern JMAP webmail for Stalwart"
    ADMIN_PASSWORD: "Test12345"
    SESSION_SECRET: "Test12345"
    SETTINGS_SYNC_ENABLED: "true"
    SETTINGS_DATA_DIR: "/app/data/settings"
    ADMIN_CONFIG_DIR: "/app/data/admin"
    ADMIN_STATE_DIR: "/app/data/admin-state"
    TELEMETRY_DATA_DIR: "/app/data/telemetry"
    LOG_LEVEL: "info"

[rathlinus]

You have to set at least one mailserver

[al-lac]

Got it. This seems to have worked, thanks! But when I access the admin panel via http://host.local/admin the login fails because it seems to require https. Any way to get this to work via http?

[ovizii]

Any link to bulwark docs describing this setup token? The search did not find anything besides this page: https://bulwarkmail.org/docs/deployment/docker#persistent-volumes which simply says:

Admin runtime state (ADMIN_STATE_DIR) - new in 1.6.4

Runtime mutations that must always stay writable: admin-state.json (login timestamps), audit.log, and the bootstrap setup token. Default: ./data/admin-state → /app/data/admin-state in the container.

[rathlinus]

if you want to set via env just set the env and a admin password

[al-lac]

Yeah, absolutely. Thanks for explaining your reasoning, I get where you are coming from.

My main concern is setups like Umbrel, Runtipi, etc., where the setup key could be set via env var, but then presented to the user in the web UI instead of requiring Docker logs.

Env vars alone work, but they skip the web setup flow entirely. In locked-down local environments, it could also be feasible to optionally skip the setup token altogether.

I think this would make the app easier to deploy for more users.

[rathlinus]

Lets do it like this: You set the admin password, and on first admin login it shows the installer again

[al-lac]

That would be great! Is this something that is already live or do you need to build it?

[rathlinus]

it is not done