Garden is a development orchestrator for Kubernetes, containers and functions, designed to make it easy to rapidly develop and test multi-service systems.
Using Garden, you can make your workflow reproducible and portable. With Garden, each part of your stack describes itself using simple, intuitive declarations, without changing any code.
Garden collects all of your declarations—even across multiple repositories—into a full graph of your stack, and leverages that information to dramatically improve your developer experience.
If you’re using Garden or if you like the project, please ★ star this repository to show your support 💖
Spin up your whole stack with a single command, and (optionally) watch for changes. Because of the dependency graph, only what's needed gets re-built, re-deployed, and/or re-tested, so you get much faster feedback loops.
Easily write integration test suites that have runtime dependencies. Run tests before pushing your code to CI, and avoid having to mock or stub your own services.
Define tasks that run as part of your deployment process, e.g. database migrations or scaffolding.
Hot reload lets you near-instantaneously update code and static files in containers as they run, for services that support in-place reloading.
Remote sources support allows your project to automatically pull code from different repositories.
The built-in web dashboard gives you a full overview of your stack (and many more UI features are planned to further aid with development).
Build, test and deploy Docker containers, Helm charts, OpenFaaS functions and more.
An extensible plug-in system ensures you'll later be able add anything that's not on this list, or create custom module types tailored to your needs (due in March 2019).
Note: The project is in alpha stage. APIs may change, and some features are still experimental.
You can find the full Garden documentation at https://docs.garden.io.
Basics, for installation instructions, our quick start guide, and an overview of the main concepts around Garden.
Using Garden, for features and usage, Garden configuration files, usage with remote clusters, and setting up hot reload.
Reference, for the glossary, commands reference, configuration files reference, and template strings reference.
There are examples of how to use Garden in a myriad of different ways in the examples folder of our repository.
For written guides based on some of these examples, check out the examples section of our documentation.
Here are some simple examples of how Garden configuration files look:
kind: Moduletype: helmname: redisdescription: Redis service for message queueingchart: stable/redis
kind: Moduletype: openfaasname: hello-functiondescription: My OpenFaaS functionlang: node
kind: Moduletype: containername: go-servicedescription: Go service containerservices:- name: go-serviceports:- name: httpcontainerPort: 80ingresses:- path: /hello-goport: httptests:- name: integcommand: [./test]dependencies: [my-other-service]
Please browse our examples directory for full project configurations and further context.
Please join the Garden Slack workspace to ask questions, discuss how Garden might fit into your workflow, or even just chat about all things DevOps.
Garden would not be possible without an amazing ecosystem of open-source projects. Here are just some of the projects that Garden uses, either directly or indirectly:
Garden, as a company, is also a proud member of the CNCF.
Garden is licensed according to Mozilla Public License 2.0 (MPL-2.0).