caddy-json-schema
ingress
caddy-json-schema | ingress | |
---|---|---|
1 | 3 | |
121 | 13,202 | |
- | - | |
0.0 | 9.7 | |
almost 2 years ago | almost 2 years ago | |
Go | Go | |
Apache License 2.0 | 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.
caddy-json-schema
-
Show HN: Caddy v2.5.0
Thanks for recommending it!
I hear ya. The JSON config is definitely not trivial. I wrote our JSON docs and strove to made them easy to follow. You can traverse into the module structure piece-by-piece here: https://caddyserver.com/docs/json/
There is also a Caddy plugin by @abiosoft that can generate a JSON schema for your custom Caddy builds, which can then be used by IDEs to give you autocomplete and validation: https://github.com/abiosoft/caddy-json-schema
I also sometimes recommend writing your config by hand in the Caddyfile, then using `caddy adapt` to get the JSON equivalent. (It might not always be the prettiest JSON, since the adapter is only so smart.) But then you can fine-tune the JSON a little easier, possibly. Hope that helps!
ingress
-
Expose multiple backends with multiple IPs with Kubernetes Ingress resources
I exposed a service with a static IP and an Ingress through an nginx controller as one of the examples of the kubernetes/ingress repository. I have a second LoadBalancer service, that is not managed by any Ingress resource that is no longer properly exposed after the adding the new resources for the first service (I do not understand why this is the case).
-
How to set up kubernetes NGINX ingress in AWS and SSL termination
I've deployed ingress controller from https://github.com/kubernetes/ingress/tree/master/examples/aws/nginx
-
Ingress responding with 'default backend - 404' when using GKE
I have read and tried pretty much everything that I could find, including stuff from here and here and here, but maybe I'm just missing something... any ideas?
What are some alternatives?
acmez - Premier ACME client library for Go
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes
ingress - WIP Caddy 2 ingress controller for Kubernetes
kubernetes-ingress - NGINX and NGINX Plus Ingress Controllers for Kubernetes
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
certmagic - Automatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
nginx-proxy - Automated nginx proxy for Docker containers using docker-gen
ingress-gce - Ingress controller for Google Cloud
go-esi - Pure implementation of the non-standard ESI (Edge-Side-Include) specification in Go
kubectl-aliases - Programmatically generated handy kubectl aliases.