mirror of https://github.com/DayuanJiang/next-ai-draw-io.git synced 2026-10-08 18:57:47 +08:00

Files

T

dayuan.jiang 69fb66804d feat(settings): reorganize the settings dialog and the model settings

Tabs Models, General, Drawing and About, each with a fixed title row.

The models tab becomes three pages: the user's providers with one status
each and the server's models; a searchable picker of all 24 providers in
four groups; and a provider page in three steps (connection, models,
test). A new provider gets its first suggested model, and a passing test
offers to use the model in the chat. Bedrock asks for one way of signing
in, with an optional session token for temporary access keys.

The composer's model picker lists every model, marking untested and
failed ones, and can open the provider picker. A chat error that offers
model settings opens the provider the request went to.

2026-10-08 17:44:08 +09:00

1.5 KiB

Raw Blame History

Admin Panel

Instead of hand-editing .env, you can manage server settings in a web admin panel.

Enabling the panel

Set the ADMIN_PASSWORD environment variable (leave unset to disable the panel).
Visit /admin and sign in.

What you can configure

Models — add providers with their API keys and model lists; the credential fields are the same as in the in-app model settings. Saved models become server-side models available to all users, merged with any AI_MODELS_CONFIG / ai-models.json from your environment at request time (the panel does not modify those env files).
Other sections — access codes, generation parameters, features, observability, and quota. Saved settings are written to data/settings.json and apply immediately — no restart needed (a few settings such as Langfuse and DynamoDB are marked "Restart Required").

Precedence

Settings saved in the panel override environment variables, which override built-in defaults. Removing a saved value falls back to the environment variable.

Notes

Secrets are stored in plaintext in data/settings.json (file mode 600). Keep the file private.
On serverless platforms (Vercel, Cloudflare Workers) there is no persistent disk, so the panel is read-only — configure via environment variables there.
With Docker, the data/ directory is persisted via the volume in docker-compose.yml.
NEXT_PUBLIC_* variables are baked in at build time and cannot be changed in the panel.

1.5 KiB Raw Blame History