What's new
- One installer for self-hosted stacks.
scripts/install.shasks which release to run and which components to use, writes the env file and starts the stack. Every question defaults to what an installation does today, so pressing Enter through it changes nothing. Answers can come from a file or the environment for unattended installs, and the installer prints the release and the component versions it was tested with when it finishes. - Your choice of components: Keycloak 24, Keycloak 26 or your own Keycloak server; a direct PostgreSQL role with
CREATEDB/CREATEROLEfor applications that need connection settings PgBouncer does not pass through; PgBouncer on all interfaces, this host only, or not published; the document store on or off; hosts without internet access. - Upgrades you can undo.
scripts/install.sh upgradebacks up every database, moves to the release you pick and goes back by itself if the API does not come up.rollbackandrestore <backup>are the explicit ways back. - Mail over SMTP. Platform mail can go through your own SMTP server, and Keycloak's own mail (password resets, verification) can use the same server.
- An AI switch. With
AI_ENABLED=falseno request reaches a hosted model provider, and embeddings are off. - A first administrator. A new installation creates its default plans on first start, and
scripts/install.sh root <email>makes the account you signed up with a platform administrator.
Fixes
- Dashboard sign-in works on Keycloak 25 and newer, which leave the user id and e-mail out of the sign-in token by default.
- A new installation whose database superuser has a custom name now locks the platform database to that user as intended.
- The release notes on GitHub list the component versions each release was tested with and whether it changes the database.