charts
Recipes
charts | Recipes | |
---|---|---|
17 | 61 | |
- | 4,958 | |
- | 1.3% | |
- | 9.9 | |
- | 7 days ago | |
Python | ||
- | GNU General Public License v3.0 or later |
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.
charts
-
Show HN: Etcha – Infinite scale, serverless config management
This may be quite clear in its simplicity, and particularly to those familiar with etcha/jsonnet. However, what invariably happens is that you start seeing things like vars embedded in templates, embedded in the config mgmt implementation language, embedded in strings. The source of the values becomes incredibly difficult to reason about and to make changes against; does the value come from the target host's env, from the runner's env, from the packaging step's env, from a network request made by one of these stages (eg to a secret server), etc.
Take a look at an example of what, IMO, is an absolutely horrid helm chart that Gitlab ships for installing their CI/CD runner: https://gitlab.com/gitlab-org/charts/gitlab-runner/-/blob/ma...
Bash code, in yaml, in golang template. Besides even the most advanced IDEs failing to grok such a freak of technical nature, there's no way I would believe any dev that told me they understand what the state of their system will be given some input to this morass.
In a recent position I was asked to try and make a nomad installation viable in a pretty standard corporate environment (not some special operational space e.g. cloudflare), and it was even worse; some configuration expansion was 5 layers deep, with 3 different templating engines, once consul templates were involved in generating an app's config, and the nomad config being env-generalized through generation by a higher-level helm-like tooling.
Re state bag:
I'm glad you mentioned nix, as I think it, and to a looser extent containers, really approach the issue in the only humanly-tenable fashion (again IMO): starting mutation from a known state. In a lot of cases that state is "nothing" as it's the simplest known state not only to position the beginning of some configuration flow at, but also the most straight-forward from which to deterministically derive a desired end state from.
I definitely applaud having tests as a core component of your system, the problem is that you can not derive determinism from nondeterminism even with the best tests.
Because you are operating over a nondeterministic bag of state, you can never guarantee that your tests provide a representation of a transfrom from any potential state to the desired end state, only for some particular input state (or set) which may or may not representative of what is found on the actual targets.
-
GitLab container image without extra applications
Here is the source for the GitLab Helm Chart. GitLab doesn't store the images for the GitLab Helm Chart on DockerHub; they store them in GitLab Registry. For example, the web service image by default is registry.gitlab.com/gitlab-org/build/cng/gitlab-workhorse-ee. This is listed here.
-
Why We’re Sticking with Ruby on Rails at Gitlab
It kind of feels like Sid is lying through his teeth here, as a person who deploys and maintains a private Gitlab installation, along with a whole host of other core platform services for internal use. Gitlab is by far the most modular off-the-shelf product I've encountered outside of JFrog's Xray. Look at their official Helm chart: https://gitlab.com/gitlab-org/charts/gitlab. Gitlab itself consists of 14 sub-charts and it also bundles 4 third-party sub-charts for object storage, a web proxy and ingress controller, certificate management, and the internal container registry. Gitlab without the third parties I believe consists of 15 distinct containers.
I don't think it matches what most people think of when they hear "monolith." It is absolutely not a single process only communicating between components via function calls. Many of the Gitlab core services, such as Gitaly, are written in Go, as well, not Ruby, though they also have "gitaly-ruby" as a testing service that can be used by developers not comfortable with Go.
- i have a gitlab runner kubernetes executer deployed thru helm chart.
-
How to Deploy to Kubernetes with Gitlab?
https://docs.gitlab.com/charts/ https://gitlab.com/gitlab-org/charts/gitlab
-
🍲 Tandoor Recipes v1.0 Release - Self-Hosted recipe manager
The GitLab Docker install instructions are for a monolithic image, but they do have separate images at https://gitlab.com/gitlab-org/build/CNG with Helm charts to configure them at https://gitlab.com/gitlab-org/charts/gitlab/-/tree/master/
-
Securing access to Scaleway Elements API Keys from Gitlab CI
[1] https://www.scaleway.com/en/docs/compute/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2/ [2] https://gitlab.com/gitlab-org/charts/gitlab-runner/-/blob/main/values.yaml [3] https://about.gitlab.com/blog/2017/09/05/how-to-automatically-create-a-new-mr-on-gitlab-with-gitlab-ci/
-
Adding GitOps/CI/CD to a maturing organization starting to utilize AWS EKS more - do we put GitOps server in production EKS cluster or new standalone EKS cluster? Catch-22?
For work we're on Gitlab Enterprise, but I run custom ci runners from the chart. They're registered to my org, so any project in my org can issue jobs.
-
Is it possible to get "gitlab-runners+container-registries" to work without LetsEncrypt.
Error logging in to endpoint, trying next endpoint" error="Get https://registry.192.168.49.2.nip.io/v2/: x509: certificate signed by unknown authority" Looking at the certificate: - Issuer: O = default, OU = gitlab, CN = GitLab Helm Chart - Subject: CN = 192.168.49.2.nip.io Steps to reproduce: (1) minikube start --addons=registry,dashboard,ingress \ --apiserver-names=apiserver.k8s,apiserver.kube-system.svc.cluster.local \ --apiserver-ips=192.168.49.2 (2) https://gitlab.com/gitlab-org/charts/gitlab.git (3) cd gitlab helm dep update helm upgrade --install gitlab . \ --timeout 600s \-f values-examples/values-minikube.yaml \ --set global.hosts.domain=$(minikube ip).nip.io \ --set global.hosts.externalIP=$(minikube ip) (4) push a random spring job into it https://github.com/paulczar/spring-helloworld
-
How to change the max memory in gitlab runners
https://gitlab.com/gitlab-org/charts/gitlab-runner/blob/master/values.yaml#L432
Recipes
- Google Says the Reddit Blackout Made Search Worse
-
Share with us your docker setup.
For recipes, I highly recommend Tandoor
-
Tandoor 1.5 - Food Properties, Unit Conversion and the Tandoor Open Data Project
Release 1.4.8 significantly improved lots of UIs, adding better navigation and dedicated layouts to mobile versions and cleaning up lots of old pages
-
Tandoor recipe page slow
Thanks. Don't think it's Synology. It's related to search display. If I pick a sort it's much faster. I actually saw a thread on your Github about it. https://github.com/TandoorRecipes/recipes/issues/2035
-
Workflow: Getting IRL Recipies into Mealie
Tandoor Was developed initially for that, to import your pdf collection of recipes. It has now evolved to be much more than that and personally prefer it to Mealie, could be worth trying!
- Self-Hosted, Docker-free, recipe manager
- I'd like an estimate for a cooking and recipe related website
-
How do you all record recipes?
With a selfhosted website purpose built for such: https://github.com/TandoorRecipes/recipes
-
Using local network mariadb with docker tandoor?
I'm trying to setup tandoor running in a docker image but I want it to use a mariadb server running on a(nother) machine on the local network. I'm trying to do this by following the instructions here: https://github.com/TandoorRecipes/recipes/discussions/246: set the POSTGRES_* environment vars to point at the mariadb host/user/db name, change the django DB_ENGINE var, and make sure mysql client packages are in the requirements.txt, and rebuild the docker image. All that seems to work and I have a local image that should want to use mariadb instead of postgres.
-
looking for a pantry / recipe / grocery app
These are both on my to look through list (I haven't yet fully looked into them and got them running) but I shortlisted 2 potential solutions for this a while ago (not all requirements are covered): https://github.com/TandoorRecipes/recipes https://hay-kot.github.io/mealie/
What are some alternatives?
v4
mealie - Mealie is a self hosted recipe manager and meal planner with a RestAPI backend and a reactive frontend application built in Vue for a pleasant user experience for the whole family. Easily add recipes into your database by providing the url and mealie will automatically import the relevant data or add a family recipe with the UI editor
brittanychiang.com v4 - Fourth iteration of my personal website built with Gatsby
Portainer - Making Docker and Kubernetes management easy.
recipes - Application for managing recipes, planning meals, building shopping lists and much much more! [Moved to: https://github.com/TandoorRecipes/recipes]
grocy - ERP beyond your fridge - Grocy is a web-based self-hosted groceries & household management solution for your home
Scaleway-cli - Command Line Interface for Scaleway
AMP - Issue tracking and documentation for AMP
flannel - flannel is a network fabric for containers, designed for Kubernetes
reverse-proxy-confs - These confs are pulled into our SWAG image: https://github.com/linuxserver/docker-swag
wireguard-windows - Download WireGuard for Windows at https://www.wireguard.com/install . This repo is a mirror only. Official repository is at https://git.zx2c4.com/wireguard-windows
RecipeSage-selfhost - A collection of configuration files to host your own private instance of RecipeSage for personal use.