Hey everyone! :wave: We're doing a prototype to t...
# prefect-community
u
Hey everyone! ­čĹő We're doing a prototype to test out prefect and plan to go with cloud version for staging and production usage, but need to do local development story too and we want to have everything managed by docker-compose locally (and potentially for CI). Unless I'm missing something, https://hub.docker.com/r/prefecthq/prefect assumes you're going to install prefect on host machine and then
prefect
would start it's containers? Is that correct? If so, what's the best path to have everything as a docker-compose file that developers can spin up on request? Ar there any samples for that use case?
Ôťů 1
­čĹő 2
a
we have a user contribution here https://discourse.prefect.io/t/docker-compose-to-run-prefect-2-0-locally-with-postgres/916 but I would strongly encourage you to install locally in a virtual environment without Docker since it's waaay easier - no weird bind mounts, port forwarding etc, pure Pythonic experience The only thing that may be helpful to run in docker is Postgres DB and for that we use this Docker compose file internally:
Copy code
version: "3.8"
services:
  test-db:
    image: postgres:13
    ports:
      - 15432:5432
    environment:
      POSTGRES_USER: prefect
      POSTGRES_PASSWORD: prefect
      POSTGRES_DB: orion
      LANG: 'C.UTF-8'
      LANGUAGE: 'C.UTF-8'
      LC_ALL: 'C.UTF-8'
      LC_COLLATE: 'C.UTF-8'
      LC_CTYPE: 'C.UTF-8'
    tmpfs: /var/lib/postgresql/data
­čÖî 1
u
yeah, i was thinking of that for first pass prototype, but we try to put as much stuff in docker so that when new people join they don't need to worry with 25 custom scripts to run prior to being ­čÜÇ productive ­čśŐ
­čĹŹ 1
But that definitely looks promising, I'll take a look, thank you @Anna Geller!
managed to execute the test job, thanks again!
­čÖî 1
a
nice work!