Ankit
07/07/2020, 12:04 PMZachary Hughes
07/07/2020, 12:58 PMAnkit
07/07/2020, 1:51 PMZachary Hughes
07/07/2020, 1:59 PMprefect server start
? I think I might be misunderstanding something about your use case.Ankit
07/07/2020, 2:07 PMprefect server start
inside it. So that, i'd only have to run docker-compose -f docker-compose.prefect.yml up
to run the entire thing.
Sorry, if I am confusing you a bit here. 😅version: "3"
services:
scheduler:
image: daskdev/dask:2.16.0
command: dask-scheduler
volumes:
- scheduler:/tmp
ports:
- 8787:8787
- 8786:8786
environment:
- DASK_DISTRIBUTED__SCHEDULER__WORK_STEALING=False
networks:
- dask
prefect-service:
image: "prefecthq/prefect:${PREFECT_SERVER_TAG:-latest}"
command:
- prefect server start
Zachary Hughes
07/07/2020, 2:27 PMAnkit
07/07/2020, 3:18 PMprefect server start
internally uses Dockerfile
and docker-compose
. So i guess i'll do with those commands for now.
Another question @Zachary Hughes is, whenever my prefect container starts/restarts do I have to re-register all the flows that I had prior to the restart? Or is it saved somehow? If I have to then is there any option to register all the scripts present in a folder or something similar?Zachary Hughes
07/07/2020, 3:56 PM--use-volume
flag when spinning up server for continued persistence.
If you don't want to persist items between instances of Prefect Server, your best bet would be to write a script that registers each flow in a given directory with Prefect Server.Ankit
07/07/2020, 3:58 PM--use-volume
option you mentioned, see if it's helpful. Thanks a lot! 😃Zachary Hughes
07/07/2020, 3:59 PM