djinn
atuin
djinn | atuin | |
---|---|---|
20 | 54 | |
39 | 17,775 | |
- | 3.0% | |
7.1 | 9.7 | |
6 months ago | 6 days ago | |
Go | Rust | |
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:
atuin
-
Ask HN: Any tool for managing large and variable command lines?
I've heard good things about atuin
https://github.com/atuinsh/atuin
-
ohmyzsh VS atuin - a user suggested alternative
2 projects | 22 Feb 2024
The shell history autocomplete seems to be better than the one that comes with Oh My Zsh.
-
Atuin – Magical Shell History
Atuin is lovely, although I found some of its defaults pretty annoying until I changed them:
- It turns out I basically never want fuzzy search through my command history, and certainly not by default. I gave it a try for a couple weeks but it was very frustrating to be searching for a particular command, type in the exact prefix, and have the thing I was looking for hidden among hundreds of irrelevant entries. Solution: search_mode = "fulltext" in Atuin's config.toml
- Having a full screen pop-up appear whenever I hit up was really jarring, especially since I have a habit of hitting up a few times when I'm at the command line thinking of what I need to do next, to sort of refresh my memory on what I was just doing; the popup very effectively destroyed that chain of thought. Solution: eval "$(atuin init bash --disable-up-arrow)" in .bashrc
These are pretty minor issues and it's possible my preferences are just different from most!
Atuin now works really nicely for me. My only outstanding issues are:
- Under mosh the UI ends up corrupting the screen; apparently this is really more of a mosh bug (no alternate screen support) and you can work around it by having tmux/screen running: https://github.com/atuinsh/atuin/issues/1324
- I still don't have a great model in my head of how sync works and find myself occasionally force-syncing across a few systems until I convince myself everything is in the same state.
- It would be nice to have some kind of settings sync so I don't have to make the config changes mentioned above on 10 different systems. Surprisingly I don't see a feature request for this yet so maybe I'll go open one...
Anyway I don't want these issues to stop people from trying Atuin – it's a really nice piece of software. I almost never make changes to the default environment so I consider it a testament to how useful it is that I've added it to all the systems I use regularly!
- Fly through your shell history
- Atuin replaces your existing shell history with a SQLite database
-
fish-shell: the user-friendly command-line shell
They recently added sqlite backed history. You can also use atuin[1] for more advanced usecases.
[1]: https://github.com/atuinsh/atuin
- Atuin: Sync and search shell history
- Ask HN: Share a shell script you like
-
Returning `Result<()>`
I was studying the Atuin crate, and I noticed the following pattern:
-
Kera Desktop: open-source, cross-platform, web-based desktop environment
You might be interested in https://github.com/ellie/atuin
> Atuin replaces your existing shell history with a SQLite database, and records additional context for your commands.
What are some alternatives?
gatus - ⛑ Automated developer-oriented status page
mcfly - Fly through your shell history. Great Scott!
tracetest - 🔭 Tracetest - Build integration and end-to-end tests in minutes, instead of days, using OpenTelemetry and trace-based testing.
fzf - :cherry_blossom: A command-line fuzzy finder
packj - Packj stops :zap: Solarwinds-, ESLint-, and PyTorch-like attacks by flagging malicious/vulnerable open-source dependencies ("weak links") in your software supply-chain
zsh-histdb - A slightly better history for zsh
onedev - Git Server with CI/CD, Kanban, and Packages. Seamless integration. Unparalleled experience.
ohmyzsh - 🙃 A delightful community-driven (with 2,300+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc), 140+ themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.
ddosify - Effortless Kubernetes Monitoring and Performance Testing. Available on CLI, Self-Hosted, and Cloud
zsh-syntax-highlighting - Fish shell like syntax highlighting for Zsh.
goimports - [mirror] Go Tools
hstr-rs - hstr, but with paging, Unicode, and fuzzy matching