vulhub
Sidekiq
vulhub | Sidekiq | |
---|---|---|
17 | 91 | |
16,220 | 12,950 | |
1.3% | 0.3% | |
8.9 | 8.9 | |
17 days ago | 6 days ago | |
Dockerfile | Ruby | |
MIT License | GNU Lesser General Public License v3.0 only |
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.
vulhub
- HackTheBox - Writeup Builder [Retired]
-
Valkey Is Rapidly Overtaking Redis
This is pretty materially not fine:
https://github.com/vulhub/vulhub/tree/master/redis/CVE-2022-...
- 2 physical computers 1 vm
-
Making sense of Apache httpd's CVE-2023-25690
I just found this commit (https://github.com/vulhub/vulhub/pull/413/files) for vulnhub containing a POC. I still don't understand exactly how they get to secret.txt in their example but it's a huge step forward. Plenty of mistakes in the Changelog.
- I am setting up a pen testing lab , I want to generate some vulnerabilities on a windows server 2019 (VM)
-
How to create vulnerable machines
A GitHub repo called vulnhub contains numerous Dockerfiles to build vulnerable containers of various popular software. If you’re just getting started this is a good way to have one machine where you deploy vulnerable docker containers to poke at.
- Vulhub: Pre-Built Vulnerable Environments Based on Docker-Compose
- How can I make a ‘bad image’ that will generate ECR scan vulnerabilities?
- Pre-Built Vulnerable Environments Based on Docker-Compose
Sidekiq
-
solid_queue alternatives - Sidekiq and good_job
3 projects | 21 Apr 2024
I'd say Sidekiq is the top competitor here.
-
Valkey Is Rapidly Overtaking Redis
There's something wrong at Redislabs, it took them over a year to get RESP3 rolled out into their hosted service, you'd expect a rollout of that to be a bit quicker when they're the owner of Redis.
It affected us when upgrading Sidekiq to version 7, which dropped support for older Redis, and their Envoy proxy setup didn't support HELLO and RESP3: https://github.com/sidekiq/sidekiq/issues/5594
-
Redis Re-Implemented with SQLite
That depends on how the `maxmemory-policy` is configured, and queue systems based on Redis will tell you not to allow eviction. https://github.com/sidekiq/sidekiq/wiki/Using-Redis#memory (it even logs a warnings if it detects your Redis is misconfigured IIRC).
-
3 one-person million dollar online businesses
Sidekiq https://sidekiq.org/: This one started as an open source project, once it got enough traction, the developer made a premium version of it, and makes money by selling licenses to businesses.
-
Choose Postgres Queue Technology
Sidekiq will drop in-progress jobs when a worker crashes. Sidekiq Pro can recover those jobs but with a large delay. Sidekiq is excellent overall but it’s not suitable for processing critical jobs with a low latency guarantee.
https://github.com/sidekiq/sidekiq/wiki/Reliability
-
We built the fastest CI in the world. It failed
> I'm not sure feature withholding has traditionally worked out well in the developer space.
I think it's worked out well for Sidekiq (https://sidekiq.org). I really like their model of layering valuable features between the OSS / Pro / Enterprise licenses.
-
Exploring concurrent rate limiters, mutexes, semaphores
I was studying Sidekiq's page on rate limiters. The first type of rate limiting mentioned is the concurrent limiter: only n tasks are allowed to run at any point in time. Note that this is independent of time units (e.g. per second), or how long they take to run. The only limitation is the number of concurrent tasks/requests.
- Ask HN: What are some of the most elegant codebases in your favorite language?
- Sidekiq and managing resumable jobs?
-
Organize Business Logic in Your Ruby on Rails Application
The code above isn't idempotent. If you run it twice, it will create two copies, which is probably not what you intended. Why is this important? Because most backend job processors like Sidekiq don't make any guarantees that your jobs will run exactly once.
What are some alternatives?
docker-openvpn-client-socks - Expose an OpenVPN tunnel as a SOCKS proxy
Resque - Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.
docker-bloodhound - BloodHound Docker Ready to Use
Sneakers - A fast background processing framework for Ruby and RabbitMQ
SniDust - SmartDNS Proxy to hide your GeoLocation. Based on DnsDist and nginx
Shoryuken - A super efficient Amazon SQS thread based message processor for Ruby
docker-dev-ssl-proxy - A simple nginx proxy behind a self-generated & self-signed SSL certificate (local HTTPS). Also utilized in development of https://speaker.app / https://github.com/zenOSmosis/speaker.app.
Sucker Punch - Sucker Punch is a Ruby asynchronous processing library using concurrent-ruby, heavily influenced by Sidekiq and girl_friday.
frigate-synology-dsm7 - Dockerfile and docker-compose file to enable google coral USB accelerators in containers on Synology DSM 7
Apache Kafka - Mirror of Apache Kafka
asterisk-docker - Asterisk + chan_dongle in docker.
celery - Distributed Task Queue (development branch)