acme-companion
ingress-nginx
acme-companion | ingress-nginx | |
---|---|---|
32 | 203 | |
7,267 | 16,664 | |
0.5% | 0.7% | |
7.4 | 9.6 | |
about 1 month ago | 8 days ago | |
Shell | Go | |
MIT License | 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.
acme-companion
-
Wireguard (docker-compose) has stopped being able to connect to the internet.
My hunch is that because I decided to include the acme-companion image in this nginx setup, that maybe it has something to do with the SSL certs? The only other thing I could think of is that I had to combine the networks in order for nginx-proxy and Sonarr both to be able to see my transmission instance via:
-
Add https to docker app
Probably want acme with nginx https://github.com/nginx-proxy/acme-companion
-
Beginner questions about deploying node.js app on Beanstalk
setting up letsencrypt with nginx-proxy and acme-companion
-
Further investigating 403 – access forbidden by rule
I'm experiencing a weird situation, and am not sure how to go about finding a solution. I am running the nginx-proxy container (https://github.com/nginx-proxy/nginx-proxy) together with the acme-companion container (https://github.com/nginx-proxy/acme-companion) to provide https connections to all my different applications under different subdomains on the same host (currently, for testing purposes: only two other nginx containers with a plain html page).
-
What is the correct way to have my webapp in one container and the webserver in another?
We use the nginx-proxy docker image with its acme-companion to have an auto configuring SSL reverse proxy, so it's really easy to deploy images (we do it based on a merge PR into protected release branches).
-
adding an SSL cert to a docker container
Use a reverse proxy to handle TLS/SSL encryption. I find nginx-proxy with companion easy to use, just follow steps 1, 2, 3.
-
502 Bad Gateway: Nginx Reverse Proxy + Docker + Let's Encrypt + Wordpress
Where I'm running into issues is with the two stacks I have deployed - one is a wordpress stack which uses the wordpress image along with a db image (going by the docs here), and the other is the nginx-proxy and acme-companion (going by the docs here).
-
dockerfile for httpd
Just use nginx-proxy and the LetsEncrypt companion as reverse proxy to handle TLS/SSL in front of your web server.
-
nginx-proxy-manager abandoned?
You can simply use this proxy container which automatically generates nginx config based on envs set in your containers. There is also a companion container which takes care of your certs. https://github.com/nginx-proxy/nginx-proxy https://github.com/nginx-proxy/acme-companion
-
Tools for automation and daily tasks
https://github.com/nginx-proxy/acme-companion https://github.com/nginx-proxy/docker-gen https://github.com/projectdiscovery/dnsx https://github.com/projectdiscovery/httpx https://github.com/projectdiscovery/mapcidr https://github.com/debauchee/barrier https://github.com/stedolan/jq https://github.com/ddosify/ddosify https://github.com/kubernetes-sigs/kind https://github.com/mailcow/mailcow-dockerized https://github.com/motiv-labs/janus
ingress-nginx
-
Automating EKS Deployment and NGINX Setup Using Helm with AWS CDK in Python
# Add NGINX ingress using Helm eks.HelmChart( self, "NginxIngress", cluster=cluster, chart="ingress-nginx", repository="https://kubernetes.github.io/ingress-nginx", namespace="ingress-nginx", values=helm_values )
-
deploying a minio service to kubernetes
ingress-nginx
-
Upgrading Hundreds of Kubernetes Clusters
The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.
-
[06/52] Accessible Kubernetes with Terraform and DigitalOcean
resource "helm_release" "icrelease" { name = "nginx-ingress" repository = "https://kubernetes.github.io/ingress-nginx" chart = "ingress-nginx" version = "4.9.1" namespace = kubernetes_namespace.icnamespace.metadata[0].name set { name = "controller.ingressClassResource.default" value = "true" } }
-
Deploy Ghost with MySQL DB replication using helm chart
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace -f custom/ghost/nginx.yaml
-
Kubernetes Gateway API v1.0: Should You Switch?
For example, if you chose Nginx Ingress, you will use some of its dozens of annotations that are not portable if you decide to switch to another Ingress implementation like Apache APISIX.
- nginx ingress controller installation
-
IP-Whitlisting: Is adjusting nginx-ingress-controller service a solution?
The controller is installed with helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace
-
Deploy Rancher on AWS EKS using Terraform & Helm Charts
helm repo add jetstack https://charts.jetstack.io helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo add rancher-latest https://releases.rancher.com/server-charts/latest helm repo update helm repo list
-
☸️ Kubernetes NGINX Ingress Controller: 10+ Complementary Configurations for Web Applications
Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.
What are some alternatives?
docker-compose-letsencrypt-nginx-proxy-companion - Automated docker nginx proxy integrated with letsencrypt. [Moved to: https://github.com/evertramos/nginx-proxy-automation]
traefik - The Cloud Native Application Proxy
nginx-proxy - Automated nginx proxy for Docker containers using docker-gen
emissary - open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
Docker Compose - Define and run multi-container applications with Docker
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
cilium-cli - CLI to install, manage & troubleshoot Kubernetes clusters running Cilium
docker-letsencrypt-nginx-proxy-companion - LetsEncrypt companion container for nginx-proxy [Moved to: https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion]
haproxy-ingress - HAProxy Ingress
nginx-proxy-automation - Automated docker nginx proxy integrated with letsencrypt.
application-gateway-kubernetes-ingress - This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.