---
title: "Object-store setup in the installer"
date: "2026-04-22"
---

## Configure storage from the browser wizard

The install wizard now includes an Object store step, so hosted deployments can choose local disk or AWS S3 before the server starts serving normal traffic. The wizard manages SlateDB and artifact storage together, which prevents the common setup mistake of putting run events in one backend and artifacts somewhere else.

```toml
[server.slatedb]
provider = "s3"
disk_cache = true

[server.slatedb.s3]
bucket = "{{ env.SLATEDB_BUCKET }}"
region = "us-east-1"
```

For AWS S3, the wizard supports runtime credentials from the deployment environment or manually entered `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. Advanced S3-compatible backends such as MinIO, R2, custom endpoints, and path-style settings remain available through manual `settings.toml` configuration.

## More

<Accordion title="CLI">
- `fabro settings --local` now reads and writes local settings without contacting a server
- Authentication-required errors now suggest `fabro auth login`
- Run dump artifact paths now use the displayed stage ID in export paths
</Accordion>

<Accordion title="Improvements">
- Dev-token handling is now gated on explicit `dev-token` auth configuration
- `fabro server start` no longer mints dev-token material when dev-token auth is disabled
- Added a Discord badge to the README
- Run status handling now uses one tagged lifecycle state representation across API and UI surfaces
</Accordion>

<Accordion title="Fixes">
- Fixed archive outcome alignment so status transitions report consistently
- Fixed server-side settings authority so unit tests and dry paths do not accidentally reach live object stores
- Fixed install runtime refresh behavior after settings updates
</Accordion>
