orc
reliza-cli
orc | reliza-cli | |
---|---|---|
1 | 10 | |
34 | 5 | |
- | - | |
1.8 | 6.8 | |
over 3 years ago | 9 days ago | |
Ruby | Go | |
MIT License | 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.
orc
reliza-cli
- Track all software deployments across all instances at any point in time with Reliza Hub
- Reliza Hub manages bundles of microservices - especially when you feel you have too many. Know what is and should be deployed on every instance at any time.
- Reliza Hub - Take Control Of All Your Software Changes
- Reliza Hub - Revolutionary Platform to Manage All Your Software Releases
-
How are you measuring DevOps performance?
We currently provide accurate lead time and deployment frequency calculation capability via Reliza Hub - https://relizahub.com (operating in public preview). Since we track when each piece of code gets deployed to each environment and each instance. Other metrics are on our roadmap.
-
Best Practices for managing parent docker images used by several services
You then either leverage getlatestrelease functionality of reliza-cli - https://github.com/relizaio/reliza-cli#6-use-case-request-latest-release-per-project-or-product to request approved image or you can use replacetags functionality over your Dockerfile which would replace base image with the one approved - https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment
- Ask HN: How do you keep track of releases/deployments of dozens micro-services?
-
How do you manage multiple environments with GitOps?
Note, we have recently released a new replacetags functionality (https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment - going to add tutorial soon) so that you don't need to use templating language inside your helm charts or manifests and instead it would just parse raw base yamls into correct images per each environment.
-
Service Config Management tools
We're building Reliza Hub for this purpose - https://relizahub.com
-
Full CI/CD pipeline delivered via ArgoCD
Note, it's somewhat outdated and we're working on a new one based on new replacetags functionality - https://github.com/relizaio/reliza-cli#72-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-instance-and-revision
What are some alternatives?
zim - A caching build system for teams using monorepos
argocd-image-updater - Automatic container image update for Argo CD
crane - ⬆ A GitLab CI ready image to upgrade services in Rancher
flux2-kustomize-helm-example - A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm.
Go - Main repository for GoCD - Continuous Delivery server
DevOpsMetrics - A project to extract and process high performing DevOps metrics (DORA) from GitHub and Azure DevOps
riff-raff - The Guardian's deployment platform
backstage - Backstage is an open platform for building developer portals
flux2-multi-tenancy - Manage multi-tenant clusters with Flux
shipit-engine - Deployment coordination
sauron - Sauron, the all seeing eye! It is a service to generate automated reports and track migrations, changes and dependency versions for backend services also report on known CVE and security issues.