https://dagster.io/ logo
Title
g

George Pearse

08/05/2021, 1:43 PM
Is it reasonable to take the python package approach (as opposed to GRPC server within docker container) when running Dagit, the dagster-daemon and Postgres within docker containers configured via docker-compose.yml ?
The hope being that it leads to a a quicker development cycle without having to rebuild the docker image for each change (or is that not the case?)
This is just for a dev config
If I run Dagit from the folder with the workspace.yml file the repos are properly recognised. If I try to run dagster via docker-compose.yml the repos are 'recognised' but do not successfully load. Sorry I'm sure I'm missing something
Oh I guess I'm copying the workspace.yaml in the docker definition (so it knows to display those repos on the UI) but then can't find the corresponding code because it's not available within the docker container (not yet copied)
d

daniel

08/06/2021, 1:09 AM
https://docs.dagster.io/deployment/guides/docker#mounting-volumes has tips for updating code without needing to rebuild the container (you do need to restart it still though). Using python_package doesnt really change when you would need to rebuild the container I don’t think.
👍 1
g

George Pearse

08/09/2021, 8:19 AM
@Daniel I haven't found a better way to update the pipeline definitions than a full
docker-compose up --build
Is it possible to update the definitions via the restart of a single container? dagster_daemon or dagster_pipelines? I have read through the docs but couldn't find anything that specifically referenced the update process.
d

daniel

08/09/2021, 12:23 PM
Yeah, you only need to restart dagster_pipelines - the other containers don’t access your code directly
❤️ 1
g

George Pearse

08/10/2021, 9:48 AM
@daniel sorry those questions were a little lazy of me, should have been able to crack that myself. Just wanted to say a huge thanks for all your help and work on dagster in general. It's a great tool and community. Hoping to get to the point I can contribute a bit back.
:condagster: 1