org | helm | |
---|---|---|
7 | 206 | |
68 | 26,045 | |
- | 1.2% | |
9.8 | 8.9 | |
about 1 month ago | 4 days ago | |
Emacs Lisp | Go | |
GNU General Public License v3.0 only | Apache License 2.0 |
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.
org
-
Org Mode Gripes
If you want to compare Org with something on Github, a better comparison would be, say, helm - undoubtly popular package developed on Github. https://github.com/helm/helm/graphs/contributors Now, look at https://github.com/yantar92/org/graphs/contributors Again, I cannot help but notice that Org is more actively developed.
-
(newbie) error with org-capture template when trying to insert or find a node
What I _think_ this means is that there is an org-capture-template with key 'd' which is trying to use some org-fold variables which are maybe not in my version of org mode yet? Relevant GitHub https://github.com/yantar92/org/blob/feature/org-fold-universal-core/README?
-
Fast note-searching with dynamic module
[2] https://github.com/yantar92/org
-
What is the largest org-mode document that you have ever created
If the slowdown is bothering you so much, you can help tesing new feature branch of Org mode with oprimised performance: https://github.com/yantar92/org
- org: Speed-up org-mode
-
Navigation in org document with 14k lines very laggy and slow
You may be interested in experimental org branch feature/org-fold. I have this org file with 2 500+ headings and 15 000+ lines and browsing it with normal org was almost impossible. On the other hand with feature/org-fold I see almost no difference when comparing browsing performance with 100 lines and few headings big org file.
helm
-
Kubernetes CI/CD Pipelines
Applying Kubernetes manifests individually is problematic because files can get overlooked. Packaging your applications as Helm charts lets you version your manifests and easily repeat deployments into different environments. Helm tracks the state of each deployment as a "release" in your cluster.
-
deploying a minio service to kubernetes
helm
-
How to take down production with a single Helm command
Explanation here: https://github.com/helm/helm/issues/12681#issuecomment-19593...
Looks like it's a bug in Helm, but actually isn't Helm's fault, the issue was introduced by Fedora Linux.
-
Building a VoIP Network with Routr on DigitalOcean Kubernetes: Part I
Helm (Get from here https://helm.sh/)
-
The 2024 Web Hosting Report
It’s also well understood that having a k8s cluster is not enough to make developers able to host their services - you need a devops team to work with them, using tools like delivery pipelines, Helm, kustomize, infra as code, service mesh, ingress, secrets management, key management - the list goes on! Developer Portals like Backstage, Port and Cortex have started to emerge to help manage some of this complexity.
-
Deploying a Web Service on a Cloud VPS Using Kubernetes MicroK8s: A Comprehensive Guide
Kubernetes orchestrates deployments and manages resources through yaml configuration files. While Kubernetes supports a wide array of resources and configurations, our aim in this tutorial is to maintain simplicity. For the sake of clarity and ease of understanding, we will use yaml configurations with hardcoded values. This method simplifies the learning process but isn’t ideal for production environments due to the need for manual updates with each new deployment. Although there are methods to streamline and automate this process, such as using Helm charts or bash scripts, we’ll not delve into those techniques to keep the tutorial manageable and avoid fatigue — you might be quite tired by that point!
-
Deploy Kubernetes in Minutes: Effortless Infrastructure Creation and Application Deployment with Cluster.dev and Helm Charts
Helm is a package manager that automates Kubernetes applications' creation, packaging, configuration, and deployment by combining your configuration files into a single reusable package. This eliminates the requirement to create the mentioned Kubernetes resources by ourselves since they have been implemented within the Helm chart. All we need to do is configure it as needed to match our requirements. From the public Helm chart repository, we can get the charts for common software packages like Consul, Jenkins SonarQube, etc. We can also create our own Helm charts for our custom applications so that we don’t need to repeat ourselves and simplify deployments.
-
Kubernets Helm Chart
We can search for charts https://helm.sh/ . Charts can be pulled(downloaded) and optionally unpacked(untar).
-
Introduction to Helm: Comparison to its less-scary cousin APT
Generally I felt as if I was diving in the deepest of waters without the correct equipement and that was horrifying. Unfortunately to me, I had to dive even deeper before getting equiped with tools like ArgoCD, and k8slens. I had to start working with... HELM.
-
🎀 Five tools to make your K8s experience more enjoyable 🎀
Within the architecture of Cyclops, a central component is the Helm engine. Helm is very popular within the Kubernetes community; chances are you have already run into it. The popularity of Helm plays to Cyclops's strength because of its straightforward integration.
What are some alternatives?
org-ql - An Org-mode query language, including search commands and saved views
crossplane - The Cloud Native Control Plane
xeft - Fast, interactive Emacs note searching
kubespray - Deploy a Production Ready Kubernetes Cluster
.emacs.d - My current Emacs setup.
Packer - Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
neovim - Vim-fork focused on extensibility and usability
krew - 📦 Find and install kubectl plugins
pbrt-v3 - Source code for pbrt, the renderer described in the third edition of "Physically Based Rendering: From Theory To Implementation", by Matt Pharr, Wenzel Jakob, and Greg Humphreys.
skaffold - Easy and Repeatable Kubernetes Development
notdeft - NotDeft note manager for Emacs
dapr-demo - Distributed application runtime demo with ASP.NET Core, Apache Kafka and Redis on Kubernetes cluster.