Chris — thanks for the reply! I saw the docker-com...
# prefect-contributors-archived
s
Chris — thanks for the reply! I saw the docker-compose but it didn’t seem complete to me. Are all the other things mentioned in the architecture currently run in the “main” docker container? (e.g. Towel — etc… )?
c
You mentioned the server docker compose file which is different from the docker compose file in the Core repo — the one I linked to is complete; in fact it’s the architecture that is spun up when users run
prefect server start
it has towel, scheduler, etc.
s
ah — got it.
c
yea the one in the server repo is purely for the persistent services (Db / hasura)
s
Great — thats quite helpful. Looking at the one in the server repo it seemed like magic to me. :)
😄 1
Well — I’ll try to get it to the point of “works for me” and then submit a PR for comments and suggestions. (Or possibly will be back here if I get stuck! :))
c
yea that sounds great! definitely feel free to reach out with questions — I think a helm chart would be really valuable
s
Yes — well … adopting prefect after kicking the tires, I somehow missed that this was missing. I certainly does fill out the core. I’ll see what I can do, though I’m sure whatever I submit will need more work for other users in other environments.
c
no worries, that sounds good
s
Chris — a quick questions when you’re back: • graphql and towel have “PREFECT_SERVER__HASURA__ADMIN_SECRET” in environment. Is this an actual secret that I should be mounting in the environment? What is its form? How come the “hasura” container doesn’t have it itself? Is it written by hasura container — so perhaps it should be a shared volume? (RW hasura, RO by the other two)?