This should make it easier to handle metadata changes like adding new routers/databases without having a chicken-and-egg problem between the DiracX container image and this repository. See #35 for a little more detail.
It does this by always overriding the DiracX container's entrypoint to optionally add pip install -e .... This also means we have to fully define the uvicorn command inside this chart, however I think this is desirable as we'll soon want to have other deployments using the same image (e.g. celery workers).
This should make it easier to handle metadata changes like adding new routers/databases without having a chicken-and-egg problem between the DiracX container image and this repository. See #35 for a little more detail.
It does this by always overriding the DiracX container's entrypoint to optionally add
pip install -e .... This also means we have to fully define the uvicorn command inside this chart, however I think this is desirable as we'll soon want to have other deployments using the same image (e.g. celery workers).Closes #35.