helm-charts
Nginx
helm-charts | Nginx | |
---|---|---|
2 | 99 | |
25 | 20,257 | |
- | 0.7% | |
7.3 | 8.8 | |
15 days ago | 10 days ago | |
Smarty | C | |
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.
helm-charts
-
GKE with Consul Service Mesh
repositories: # https://artifacthub.io/packages/helm/dgraph/dgraph/0.0.19 - name: dgraph url: https://charts.dgraph.io # https://artifacthub.io/packages/helm/main/raw - name: bedag url: https://bedag.github.io/helm-charts/ releases: # Dgraph additional resources required to support Consul - name: dgraph-extra chart: bedag/raw namespace: dgraph version: 1.1.0 values: - resources: - apiVersion: v1 kind: ServiceAccount metadata: name: dgraph-dgraph-zero - apiVersion: v1 kind: ServiceAccount metadata: name: dgraph-dgraph-alpha - apiVersion: v1 kind: ServiceAccount metadata: name: dgraph-dgraph-alpha-grpc - apiVersion: v1 kind: Service metadata: name: dgraph-dgraph-alpha-grpc spec: ports: - name: grpc-alpha port: 9080 publishNotReadyAddresses: true selector: app: dgraph chart: dgraph-0.0.19 component: alpha release: dgraph type: ClusterIP # Dgraph cluster with 2 x StatefulSet (3 Zero pods, 3 Alpha pods) - name: dgraph namespace: dgraph chart: dgraph/dgraph version: 0.0.19 needs: - dgraph/dgraph-extra values: - image: tag: v21.03.2 zero: extraAnnotations: consul.hashicorp.com/connect-inject: 'true' # disable transparent-proxy for multi-port services consul.hashicorp.com/transparent-proxy: 'false' consul.hashicorp.com/transparent-proxy-exclude-inbound-ports: "5080,7080" consul.hashicorp.com/transparent-proxy-exclude-outbound-ports: "5080,7080" alpha: extraAnnotations: consul.hashicorp.com/connect-inject: 'true' # disable transparent-proxy for multi-port services consul.hashicorp.com/transparent-proxy: 'false' # use these registered consul services for different ports consul.hashicorp.com/connect-service: 'dgraph-dgraph-alpha,dgraph-dgraph-alpha-grpc' consul.hashicorp.com/connect-service-port: '8080,9080' consul.hashicorp.com/transparent-proxy-exclude-inbound-ports: "5080,7080" consul.hashicorp.com/transparent-proxy-exclude-outbound-ports: "5080,7080" configFile: config.yaml: | security: whitelist: {{ env "DG_ACCEPT_LIST" | default "0.0.0.0/0" | quote }} # patch existing resources using merge patches strategicMergePatches: # add serviceAccountName to Alpha StatefulSet - apiVersion: apps/v1 kind: StatefulSet metadata: name: dgraph-dgraph-alpha spec: template: spec: serviceAccountName: dgraph-dgraph-alpha # add serviceAccountName to Zero StatefulSet - apiVersion: apps/v1 kind: StatefulSet metadata: name: dgraph-dgraph-zero spec: template: spec: serviceAccountName: dgraph-dgraph-zero # add label to Alpha headless service - apiVersion: v1 kind: Service metadata: name: dgraph-dgraph-alpha-headless labels: consul.hashicorp.com/service-ignore: 'true' # add label to Zero headless service - apiVersion: v1 kind: Service metadata: name: dgraph-dgraph-zero-headless labels: consul.hashicorp.com/service-ignore: 'true' # patch existing resource using jsonPatches jsonPatches: # remove existing grpc port from serivce - target: version: v1 kind: Service name: dgraph-dgraph-alpha patch: - op: remove path: /spec/ports/1
-
How are charts & manifests usually deployed together?
https://github.com/helmfile/helmfile + incubator raw
Nginx
-
Nginx 1.26.0 Stable Released
Yeah, unless I'm looking at it wrong, there doesn't seem to be any meaningful difference between 1.25.5 and 1.26.0:
https://github.com/nginx/nginx/compare/release-1.25.5...rele...
-
How to securely reverse-proxy ASP.NET Core web apps
However, it's very unlikely that .NET developers will directly expose their Kestrel-based web apps to the internet. Typically, we use other popular web servers like Nginx, Traefik, and Caddy to act as a reverse-proxy in front of Kestrel for various reasons:
- Ask HN: Is nginx.org (the domain-name itself) gone?
-
Freenginx: Core Nginx Developer Announces Fork of Popular Web Server
> I actually don't understand why I am seeing arguments like this all the time.
Have a look at:
https://github.com/nginx/nginx/blob/master/src/http/modules/...
It's got the whole checklist: nginx idiosyncratic module system, inline parsing, custom utf conversion, buffer preallocation and adjustments, linked lists, comments about side effects of custom allocator, and probably other things.
It's not easy to deal with source like that and any serious improvement to that area would effectively be a rewrite anyway.
Since anything doing work in nginx is a module anyway, it wouldn't even have to be a full rewrite in one go.
-
The Internet is Maintained by 1 Software Developer
According to this article, nGinx is being used to serve 34% of all websites in the world. I checked out who's contributing to nGinx, and just like I thought, the project has 8,208 commits, and 5,366 of those commits was made by 2 software developers; igorsoev and mdounin.
- [06/52] Accessible Kubernetes with Terraform and DigitalOcean
- Freenginx.org
-
Performance benchmark of PHP runtimes
Nginx + Roadrunner (fcgi mode)
-
Web CGI programs aren't particularly slow these days
Apache’s mod_fastcgi’s last commit was 2 weeks ago:
https://svn.apache.org/viewvc/httpd/httpd/trunk/
It’s a fork of what you linked (and was more popular afaik back when fastcgi was state of the art, and apache was the undisputed champion of web servers).
These days, nginx has more market share than apache, and its fastcgi module is one of the more recently updated ones in its source tree (5 months vs multiple years):
https://github.com/nginx/nginx/tree/master/src/http/modules
If I was going to build an embedded web server, I’d start with nostd rust, probably with though axum + tokio, since thats already memory safe-ish.
If I needed fastcgi for some reason (dynamically loadable endpoints, or os-level isolation), there are at least four implementations of fastcgi for it. No idea if any are decent though.
-
Five Apache projects you probably didn't know about
APISIX is an API Gateway. It builds upon OpenResty, a Lua layer built on top of the famous nginx reverse-proxy. APISIX adds abstractions to the mix, e.g., Route, Service, Upstream, and offers a plugin-based architecture.
What are some alternatives?
google.cloud - GCP Ansible Collection https://galaxy.ansible.com/google/cloud
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
helmfile - Declaratively deploy your Kubernetes manifests, Kustomize configs, and Charts as Helm releases. Generate all-in-one manifests for use with ArgoCD.
envoy - Cloud-native high-performance edge/middle/service proxy
hub-feedback - Feedback and bug reports for the Docker Hub
Squid - Squid Web Proxy Cache
nestjs-monorepo-microservices-proxy - Example of how to implement a Nestjs monorepo with no shared folder
consul-k8s-ingress-controllers - Testing for different API gateways with Consul
Hiawatha - Hiawatha is an open source webserver with security, easy to use and lightweight as the three key features. Hiawatha supports among others (Fast)CGI, IPv6, URL rewriting and reverse proxy. It has security features no other webserver has, like blocking SQL injections, XSS and CSRF attacks and exploit attempts. The built-in monitoring tool makes it perfect for large scale deployments.
ratel - Dgraph Data Visualizer and Cluster Manager
YARP - A toolkit for developing high-performance HTTP reverse proxy applications.