Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

hey prefect fam, do you have a docker compose template for running prefect 2 locally?

this looks outdated? <https://medium.com/the-prefect-blog/how-to-self-host-prefect-orion-with-postgres-using-docker-compose-631c41ab8a9f>

that should be roughly correct if you replace all instances of "orion" or "ORION" with "server" / "SERVER"

<https://docs.prefect.io/2.14.3/guides/host/|this page may be helpful>

since prefect ships with sqlite, we can whack the postgres container entirely, yeah?

if you're cool with sqlite then yeah you wouldnt need pg around

i'm getting this error:

```              ^^^^^^^^^^
pipelines-orion-1     | sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) database is locked
pipelines-orion-1     | [SQL: DELETE FROM flow_run_notification_queue WHERE flow_run_notification_queue.id IN (SELECT 1 FROM (SELECT 1) WHERE 1!=1) RETURNING id]
pipelines-orion-1     | (Background on this error at: <https://sqlalche.me/e/20/e3q8>)```

```networks:
  prefect:
    name: prefect

services:
  prefect-server:
    image: prefecthq/prefect:2-python3.11
    command: prefect server start
    ports:
      - 4200:4200
    environment:
      PREFECT_API_URL: <http://127.0.0.1:4200/api>
    networks:
      - prefect```

hmm i have seen that before with sqlite, when you're using pg, though have you set this?
```PREFECT_API_DATABASE_CONNECTION_URL="<postgresql+asyncpg://postgres:yourTopSecretPassword@localhost:5432/prefect>"```


fyi <@U02GMEZU18B> -- looks like that error is not problematic: <https://github.com/PrefectHQ/prefect/issues/10956>

can set this env var and it goes away with no problems:     `PREFECT_API_SERVICES_FLOW_RUN_NOTIFICATIONS_ENABLED: false`

oops, this dropped off my radar. oh - nice! glad you figured it out