nammayatri
gradle-docker-compose-plugin
| nammayatri | gradle-docker-compose-plugin | |
|---|---|---|
| 5 | 1 | |
| 1,037 | 402 | |
| 1.9% | 0.0% | |
| 10.0 | 6.9 | |
| 1 day ago | 9 days ago | |
| PureScript | Groovy | |
| GNU Affero General Public License v3.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nammayatri
-
Testcontainers
If your project uses Nix, checkout services-flake for running services via Nix.
https://github.com/juspay/services-flake
We actually do this in Nammayatri, an OSS project providing "Uber" for autos in India.
https://github.com/nammayatri/nammayatri
There is a services-flake module allowing you to spin the entire nammayatri stack (including postgres, redis, etc.) using a flake app. Similarly, there's one for running load test, which is also run in Jenkins CI.
- Namma Yatri – open-source Uber/Lyft Alternative (In active use in India)
- Open-Source, Zero Commission, Uber-Lyft Alternative for India
- I raise you this Namma Yatri notification. What do you have in return?
-
Anyone used Namma Yatri app? How’s your experience?
NY is in the early stages of growth, and there are definitely areas for improvement. Key priorities are improving affordability, customer experience & support and driver availability. But what has differentiated NY so far is its 100% openness in every decision. It's built on Beckn protocol (like open Email/SMTP or TCP/IP protocols, anyone can implement it). NY is part of ONDC network, so anyone can do what NY has done so far. Initial response is encouraging, with 5L+ customers, ~50k drivers, ~4.8 app rating (Open data here). Open Roadmap here. Complete source code here. Anyone can contribute to the open problems through city hackathon. DM your thoughts and happy to hope into a call.
gradle-docker-compose-plugin
-
Testcontainers
Something that improved developer experience by far and also sped up our builds is starting the container dependencies via docker-compose and connect to it for integration testing. This allows reuse of containers, you can connect to it after/during an integration test to debug without having to keep searching for ports constantly.
With TestContainers - I've perceived that running integration tests / a single test repeatedly locally is extremely slow as the containers are shut down when the java process is killed. This approach allows for this while also allowing to keep it consistent - example, just mount the migrations folder in the start volume of your DB container and you have a like-for-like schema of your prod DB ready for integration tests.
I've found the https://github.com/avast/gradle-docker-compose-plugin/ very useful for this.
What are some alternatives?
protocol-specifications - Core protocol specification for peer-to-peer consumer-provider interaction
services-flake - NixOS-like services for Nix flakes
latte - Latte is a modern data engineering toolkit.
otj-pg-embedded - Java embedded PostgreSQL component for testing
embedded-postgres-binaries - Lightweight bundles of PostgreSQL binaries with reduced size intended for testing purposes.
testcontainers-node - Testcontainers is a NodeJS library that supports tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container.
dagger - Application Delivery as Code that Runs Anywhere
pglite - Lightweight Postgres packaged as WASM into a TypeScript library for the browser, Node.js, Bun and Deno