DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to move a team UFO server onto Postgres with Ufo Core

Point the server at a local Postgres database before creating the workspace.

Credentials. The README example uses the default Postgres user and password ufo:ufo, so change them before the database holds real team data.

Who it is forAn ops engineer setting up a UFO server for several users who need a database that is not SQLite.

The problemThe default SQLite setup is meant for one process on one machine, and a larger deploy needs a shared database.

The outcomeA UFO server reading and writing a Postgres database named ufo, with the workspace created in that database.

What you need first

  • Python with uv installed (https://docs.astral.sh/uv/)
  • API keys for the three model providers, set in .env
  • For remote sandbox use: a hosted UFO workspace, or a self-hosted server with a configured sandbox carrier
  • For Postgres or the debugger: make and pnpm

Steps

  1. Run make db
  2. Write ufo.toml with the Postgres URL using the command in the Postgres section of the README
  3. Run make init [email protected]
  4. Run make serve

Prompt for your agent

In the ufo-core repo, run `make db`, write ufo.toml as the README's Postgres section describes, then run `make init EMAIL=<work email>` and `make serve`. Expected output: the server starts on http://localhost:8710 against postgresql+asyncpg on 127.0.0.1:5541. Verify that ufo.toml contains the postgresql+asyncpg URL before you report success.

Caveat. The README gives the Postgres connection string only for the local make db setup, and scale-out to S3 and Redis is described in one line without steps.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page