crashappsec / crashappsec/chalk
[objective] Easy Deployment Everywhere
- Dominant language
- Nim
- Stars
- 436
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
We definitely strive for friction-free deployment wherever possible; that goal led to our approach for handling docker builds, and our configuration strategy, there is a lot more that should be done, especially in making Chalk work as well as possible with a wide variety of technology stacks, not just docker builds.
There are multiple dimensions to this-- we should make it trivially easy to deploy across organizations using built in CI/CD tooling at Github/Gitlab, not to mention other popular CI/CD tools.
But we should also be thinking about how to make it easy to deploy in environments leveraging composition tools like docker bake or docker compose. Currently, without us integrating with those pieces, effectively deploying probably harder, because it would take more work than should be needed to tie data together.
Similarly, we aren't doing anything to support other container runtimes, which complicates deployments using them. We also don't cover all cases for the docker deployment we do cover, as a few scenarios will disable container wrapping (like multi-arch builds, which is pretty important in our view) and some unsupported features (like Heredocs) will cause us to fall back to a regular invocation of Docker.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.