https://github.com/flant/dapp
A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
https://github.com/flant/dapp
buildah ci-cd continuous-delivery continuous-integration devops docker docker-image dockerfile giterminism gitops golang helm iac kubernetes werf
Last synced: 7 months ago
JSON representation
A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
- Host: GitHub
- URL: https://github.com/flant/dapp
- Owner: werf
- License: apache-2.0
- Created: 2016-01-25T16:46:58.000Z (almost 10 years ago)
- Default Branch: main
- Last Pushed: 2025-02-12T10:51:10.000Z (9 months ago)
- Last Synced: 2025-02-12T11:52:46.457Z (9 months ago)
- Topics: buildah, ci-cd, continuous-delivery, continuous-integration, devops, docker, docker-image, dockerfile, giterminism, gitops, golang, helm, iac, kubernetes, werf
- Language: Go
- Homepage: https://werf.io
- Size: 44 MB
- Stars: 4,312
- Watchers: 50
- Forks: 209
- Open Issues: 133
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
Awesome Lists containing this project
- awesome-list-ansible - dapp
README
werf is a CNCF Sandbox CLI tool to implement full-cycle CI/CD to Kubernetes easily. werf integrates into your CI system and leverages familiar and reliable technologies, such as Git, Dockerfile, Helm, and Buildah.
What makes werf special:
- **Complete application lifecycle management**: build and publish container images, test, deploy an application to Kubernetes, distribute release artifacts and clean up the container registry.
- **Ease of use**: use Dockerfiles and Helm chart for configuration and let werf handle all the rest.
- **Advanced features**: automatic build caching and content-based tagging, enhanced resource tracking and extra capabilities in Helm, a unique container registry cleanup approach, and more.
- **Gluing common technologies**: Git, Buildah, Helm, Kubernetes, and your CI system of choice.
- **Production-ready**: werf has been used in production since 2017; thousands of projects rely on it to build & deploy various apps.
## Installation
The [Getting Started guide](https://werf.io/getting_started/) helps set up and use werf both locally and in your CI system.
## Documentation
Detailed usage and reference for werf are available in [documentation](https://werf.io/docs/) in multiple languages.
Developers can get all the necessary knowledge about application delivery in Kubernetes (including basic understanding of K8s primitives) in the [werf guides](https://werf.io/guides.html). They provide ready-to-use examples for popular frameworks, including Node.js (JavaScript), Spring Boot (Java), Django (Python), Rails (Ruby), and Laravel (PHP).
## Community & support
Please feel free to reach developers/maintainers and users via [GitHub Discussions](https://github.com/werf/werf/discussions) for any questions regarding werf. You're also welcome on [Stack Overflow](https://stackoverflow.com/questions/tagged/werf): when you tag a question with `werf`, our team is notified and comes to help you.
Your issues are processed carefully if posted to [issues at GitHub](https://github.com/werf/werf/issues).
For questions that may require a more detailed and prompt discussion, you can use:
* [#werf](https://cloud-native.slack.com/archives/CHY2THYUU) channel in the CNCF’s Slack workspace;
* [werf_io](https://t.me/werf_io) Telegram chat. _(There is a Russian-speaking Telegram chat [werf_ru](https://t.me/werf_ru) as well.)_
Follow [@werf_io](https://x.com/werf_io) to stay informed about all important project's news, new articles, etc.
## Contributing
This [contributing guide](https://github.com/werf/werf/blob/main/CONTRIBUTING.md) outlines the process to help get your contribution accepted.
## License
Apache License 2.0, see [LICENSE](LICENSE).
## Featured in
