ansible-collection-compositionalenterprises.ourcompose
By compositionalenterprises
acme-companion
Automated ACME SSL certificate generation for nginx-proxy (by nginx-proxy)
ansible-collection-compositionalenterprises.ourcompose | acme-companion | |
---|---|---|
3 | 32 | |
- | 7,266 | |
- | 0.5% | |
- | 7.4 | |
- | 3 days ago | |
Shell | ||
- | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
ansible-collection-compositionalenterprises.ourcompose
Posts with mentions or reviews of ansible-collection-compositionalenterprises.ourcompose.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-10-31.
-
Docker containers managed with ansible roles - how to ensure proper start up order (a la docker-compose depends_on)?
Here is the systemd service file that I use to do that: https://gitlab.com/compositionalenterprises/ansible-collection-compositionalenterprises.ourcompose/-/blob/stable-4.1/roles/portal/files/portal_ourcompose_startup.service
-
What is the cleanest way to deploy a docker-compose stack to a remote server?
That's the route we chose for OurCompose. Turns out to be really flexible for fixing other things too.
-
Docker NGINX Reverse Proxy to other containers
I have a couple of templates here that is part of my larger setup. That should give you a kickstart in the right direction.
acme-companion
Posts with mentions or reviews of acme-companion.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-10.
-
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