ddosify
acme-companion
Our great sponsors
ddosify | acme-companion | |
---|---|---|
101 | 32 | |
8,195 | 7,261 | |
0.7% | 0.8% | |
8.6 | 7.6 | |
8 days ago | about 1 month ago | |
Go | Shell | |
GNU Affero General Public License v3.0 | MIT License |
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.
ddosify
-
5 Awesome Go Projects To Know Before You Die
DDosify: https://github.com/ddosify/ddosify
-
Self-Hosted, Distributed, No-code Performance Testing Platform
We are thrilled to announce the release of Ddosify Self-Hosted on GitHub today. Unlike the Ddosify Engine, this version features a No-code UI and supports distributed traffic generation.
-
Simple, Open Source, Load Testing Tool
Ddosify is built with ease of use and flexibility in mind, and it supports popular web protocols. It allows you to define and customize test scenarios, generate realistic loads, and monitor performance metrics in real time.
-
Load Testing a Fintech API with CSV Test Data Import
We have organized this write-up into two parts to demonstrate two different features of Ddosify. In the first part, we will perform a load test on a GET endpoint that accepts base and target currency and returns their exchange rate of them. The rand() utility method is used to send different currencies on each request. In the second part, we will test a POST endpoint that performs exchange operations. We will use a CSV file that contains test data stored on our Test App's Database. Then we import this CSV file into Ddosify to replay the same transactions stored on DB, but in high concurrency. In both parts, we will gain insights into the reliability of our exchange API across high traffic.
- Simple, open-source, lightweight stress tool
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
What are some alternatives?
locust - Write scalable load tests in plain Python 🚗💨
docker-compose-letsencrypt-nginx-proxy-companion - Automated docker nginx proxy integrated with letsencrypt. [Moved to: https://github.com/evertramos/nginx-proxy-automation]
Vegeta - HTTP load testing tool and library. It's over 9000!
nginx-proxy - Automated nginx proxy for Docker containers using docker-gen
Hey - HTTP load generator, ApacheBench (ab) replacement
Docker Compose - Define and run multi-container applications with Docker
Performance-Testing-Tools - 🛠 Curated list of Performance Testing Tools ⚡ All contributions are welcome 💜
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
xk6-kafka - k6 extension to load test Apache Kafka with support for various serialization formats, SASL, TLS, compression, Schema Registry client and beyond
docker-letsencrypt-nginx-proxy-companion - LetsEncrypt companion container for nginx-proxy [Moved to: https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion]
go-wrk - go-wrk - a HTTP benchmarking tool based in spirit on the excellent wrk tool (https://github.com/wg/wrk)
nginx-proxy-automation - Automated docker nginx proxy integrated with letsencrypt.