djinn
Asynq
djinn | Asynq | |
---|---|---|
20 | 32 | |
39 | 8,648 | |
- | - | |
7.1 | 7.0 | |
6 months ago | about 6 hours ago | |
Go | Go | |
Apache License 2.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.
djinn
-
Monthly 'Shameless Self Promotion' thread - 2022/12
Djinn CI is a newly launched CI platform, with the following features:
-
Act: Run your GitHub Actions locally
I've built a CI platform [1] that does support running your CI builds without the server using an offline runner. I wrote about it here before: https://blog.djinn-ci.com/showcase/2022/08/06/running-your-c...
[1] - https://about.djinn-ci.com/
-
Djinn CI ā open-source CI platform
Author of Djinn CI here. This is a CI platform that I developed, it is open source but there is also a hosted offering https://about.djinn-ci.com. Some of the features are detailed below:
* Fully virtualized Linux VMs
* GitHub/GitLab integration
* Variable masking
* Configurable artifact cleanup limits
* Multi-repository builds
* Repeatable builds with cron jobs
* Custom QCOW2 images for builds
I've written some posts demonstrating the features of the platform which I have posted here before:
* https://blog.djinn-ci.com/showcase/2022/08/06/running-your-c...
* https://blog.djinn-ci.com/showcase/2022/08/16/using-multiple...
For further reading there is also the documentation sub-site at https://docs.djinn-ci.com/.
If you have any questions don't hesitate to reach out.
-
Blazing fast CI with MicroVMs
Good article. Firecracker is something that has definitely piqued my interest when it comes to quickly spinning up a throwaway environment to use for either development or CI. I run a CI platform [1], which currently uses QEMU for the build environments (Docker is also supported but currently disabled on the hosted offering), startup times are ok, but having a boot time of 1-2s is definitely highly appealing. I will have to investigate Firecracker further to see if I could incorporate this into what I'm doing.
Julia Evans has also written about Firecracker in the past too [2][3].
[1] - https://about.djinn-ci.com
[2] - https://jvns.ca/blog/2021/01/23/firecracker--start-a-vm-in-l...
[3] - https://news.ycombinator.com/item?id=25883253
-
From WampServer, to Vagrant, to QEMU
At this point when it came to my hobbyist development, I had moved past PHP and started learning Go, and was looking to do some serious development with this for a CI platform I had an idea for. By now, I had a firmer grasp of the software stack I wanted to work with, a better understanding of how everything pieced together. And so I went about developing that CI platform, that would later become Djinn CI. I uninstalled VirtualBox and Vagrant and fully committed to using QEMU, booting up the local machine was as simple as hitting CTRL + R in my terminal, searching for qemu and hitting enter, an elegant solution I know.
-
Looking for a mature distributed task queuer/scheduler in go
I use mcmathja/curlyq and found it pretty reliable. This is the queue I use for Djinn CI an open source CI platform I developed.
-
Using multiple repositories in your CI builds
Djinn CI makes working with multiple repositoriesin a build simple via the sourcesparameter in the build manifest. This allows you to specify multiple Git respositories to clone into your build environment. Each source would be a URL that could be cloned via git clone. With most CI platforms, a build's manifest is typically tied to the source code repository itself. With Djinn CI, whilst you can have a build manifest in a source code repository, the CI server itself doesn't really have an understanding of that repository. Instead, it simply looks at the sources in the manifest that is specified, and clones each of them into the build environment.
-
Running your CI builds without the server
Perhaps the one feature that sets Djinn CI out from other CI platforms is the fact that is has an offline runner. The offline runner allows for CI builds to be run without having to send them to the server. There are some limitations around this, of course, but it provides a useful mechanism for sanity checking build manifests, testing custom images, and for building software without the need for a CI server.
-
Show HN: OneDev ā A Lightweight Gitlab Alternative
You mention CI being done in a distributed fashion. Could you elaborate on what you mean by this?
I'm asking as I'm someone who has developed a CI platform [1], and one of its features is the offline runner [2]. The offline runner allows you to run your CI builds on your own computer, and does not communicate with the CI server whatsoever. Is this what you had in mind?
[1] https://about.djinn-ci.com
[2] https://docs.djinn-ci.com/user/offline-runner/
-
Monthly 'Shameless Self Promotion' thread - 2022/06
Djinn CI is a newly launched CI platform, with the following features:
Asynq
-
Looking for a language agnostic Go task queue with Redis
EDIT : I think the best for my case will be to use the asynq library with a custom js client, it's quite easy to implement (Detailed here)
-
I have a web app that requires allowing users to schedule a recurring task at their own specified time/interval. How would you go about it?
Asynq does this pretty nicely https://github.com/hibiken/asynq/wiki/Periodic-Tasks
-
Examples of using task scheduler with Go?
Asynq looks promising. Never used it myself. https://github.com/hibiken/asynq
-
Recommendation for a selfhosted worker/task queue runner?
Never used it, but it appears to fit most of the criteria. https://github.com/hibiken/asynq
- How to run periodic tasks?
-
What would you rewrite in Golang?
https://github.com/hibiken/asynq is pretty close
-
Suggestions for CRON jobs queue tool
I tried it 2 months ago and it was not suitable for dynamic CRON job enqueue scheduling
-
Iām looking for a suggestion for a queuing library
My current best option is AsynQ (https://github.com/hibiken/asynq but it uses redid and not Postgres for the db
-
What is the best task queue?
Hi, I'm starting a new project that involves distributing task on different (and possibly distributed) workers in Golang. So I'm looking for the best task queue library to use; for now the ones I like are the following (in no particular order): - asynq - machinery - taskq
-
Distributed queue(redis) go
Asynq might do what you need https://github.com/hibiken/asynq
What are some alternatives?
gatus - ā Automated developer-oriented status page
machinery - Machinery is an asynchronous task queue/job queue based on distributed message passing.
tracetest - š Tracetest - Build integration and end-to-end tests in minutes, instead of days, using OpenTelemetry and trace-based testing.
work - Process background jobs in Go
packj - Packj stops :zap: Solarwinds-, ESLint-, and PyTorch-like attacks by flagging malicious/vulnerable open-source dependencies ("weak links") in your software supply-chain
Faktory - Language-agnostic persistent background job server
atuin - āØ Magical shell history
NATS - Golang client for NATS, the cloud native messaging system.
onedev - Git Server with CI/CD, Kanban, and Packages. Seamless integration. Unparalleled experience.
temporal - Temporal service
ddosify - Effortless Kubernetes Monitoring and Performance Testing. Available on CLI, Self-Hosted, and Cloud
nsq - A realtime distributed messaging platform