Great to get a SRE perspective. The de-duplication uses a SQLite table using a primary key that is the SHA256 of the file contents. There is not much code on top of that. The one complexity is knowing when it is safe to actually delete a file, since it could be referenced in multiple apps.
Clace is built for use cases where teams want to be able to easily deploy Streamlit/Gradio/FastAPI type internal apps (python is supported out of the box, other languages work if they have a Dockerfile present). Clace adds the image building, GitOps, OAuth access control, blue-green staged deployment, secrets management etc on top. So use cases where Kubernetes and an IDP would be overkill for.
> The one complexity is knowing when it is safe to actually delete a file, since it could be referenced in multiple apps.
If this person is anything like me, it's this "feature" that is giving them nightmares. This code has to be rock solid and impossible for anyone to mess up. It only takes one little bug and EVERY SINGLE APP GOES DOWN. Congrats on inventing a new single-point-of-failure!
If it helps, that cleanup is not implemented currently. I did not want the cleanup to be done as part of regular app update/delete. The plan is to add a vacuum/purge type of command, which expressly does this cleanup, and document that a database backup is good to have before running that.
Clace is built for use cases where teams want to be able to easily deploy Streamlit/Gradio/FastAPI type internal apps (python is supported out of the box, other languages work if they have a Dockerfile present). Clace adds the image building, GitOps, OAuth access control, blue-green staged deployment, secrets management etc on top. So use cases where Kubernetes and an IDP would be overkill for.