Bazel_compose Alternatives

Similar projects and alternatives to bazel_compose

Docker Compose

387 32,367 9.6 Go bazel_compose VS Docker Compose

Define and run multi-container applications with Docker
skaffold

83 14,659 9.2 Go bazel_compose VS skaffold

Easy and Repeatable Kubernetes Development
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
volta

84 9,964 9.1 Rust bazel_compose VS volta

Volta: JS Toolchains as Code. ⚡
entr

47 4,002 6.8 C bazel_compose VS entr

Run arbitrary commands when files change
garden

40 3,255 9.9 TypeScript bazel_compose VS garden

Automation for Kubernetes development and testing. Spin up production-like environments for development, testing, and CI on demand. Use the same configuration and workflows at every step of the process. Speed up your builds and test runs via shared result caching
telepresence

38 6,347 9.8 Go bazel_compose VS telepresence

Local development against a remote Kubernetes or OpenShift cluster
dew

3 7 5.5 Shell bazel_compose VS dew

Run everything in (Docker) containers
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better bazel_compose alternative or higher similarity.

Suggest an alternative to bazel_compose

bazel_compose reviews and mentions

Posts with mentions or reviews of bazel_compose. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-05-31.

You Don't Need to Rebuild Your Development Docker Image on Every Code Change
9 projects | news.ycombinator.com | 31 May 2021

While this is great for people with a fundamental understanding of containers and your prod environment this will usually lead to some issues with developers that don't need to, or want to, have context in these areas.
In the past, to make a very similar workflow possible, I've built tools that automatically watch your source files and rebuild & restart only what is needed [0]. This was built for bazel + docker-compose but there isn't a reason one couldn't watch the "build:" contexts for what files are important.
At a previous company one of our engineers was a huge fan of this volume mount approach and every single time something broke (which was very frequent due to some prod/dev env magic we had) I had to assist quite a few more junior devs figure out what was wrong with their machine. For those with scripting languages, was it their system's newline endings? For compiled languages, was their system SDK different then what was in the container? For prod bugs, did they forget to rebuild & test the container before opening their PR (we had no automated integration testing)?
In my opinion, if you can make your build system in charge of building/packaging things you'll have a much happier time.
[0] - https://github.com/CaperAi/bazel_compose