DTAP is:

• fast ( both server and client side a written on go )
• it has Bash api for end users ( who would write check scenarios )
• For strict environments it allows to run checks remotely over ssh without even installing anything

Check it out and feel free to ask anything

https://dtap.sparrowhub.io/doc/checks

Thanks

Hey 👋 DSCI author here. If someone love to check out dsci please let me know. It’s in beta stage, but some essential features are here. Extremely fast and lightweight git server and cicd. Fast ci engine on Rakupp. Ability to port existing remote git repos . CI SDK supports many languages including Python, Ruby, Raku. CI jobs run on podman / docker or localhost . Authentication for git push over https. The memory and CPU footprint is comparable to forgejo. You don’t need to install extra ci runner as the one comes included . Thus is extremely simple install. Minimal operations efforts. Suites the best to small dev teams hosting things on single VPS. Works in any Linux / Mac box. Hardware requirements - 4-8 GB RAM, 50 GB hard drive. No extra dependencies like pgsql , redis etc. Backend and front end written on golang . CI engine is on Raku, but runs on Rakupp - efficient Raku implementation that gives one a minimal start up time, speed and small cpu/memory consumption - check yourself. Everything is installed as binaries …

Current demo stand https://dsci.sparrowhub.io/ runs on Rakupp , I need to tweak official documentation to reflect Rakupp migration changes ( not a lot though )

PS. This is NOT AI written project.

In this episode I talk about developing web application based on well known cro framework and specifically how to create CI pipeline using DSCI tool.

DSCI is simple yet super flexible pipeline engine to write CI code on regular programming languages, integrates with Forgejo using web hooks. Intended for small teams hosting Forgejo on single VM VPS and willing to create pipelines on regular programming languages

DTAP protocol is a lightweight testing protocol allowing to validate Linux infrastructure at ease. Here is a code example of how one can check that their Rocky Linux VM is secure enough (more Linux distributions are easy to check the same way).

Some times ago I posted about scc tool, here is a short update with some example reports provided. https://dev.to/melezhik/linux-compliance-checks-with-sparrow-plugin-2160

People can use the plugin to check if their Linux configuration files are security compliant

Sparrow is a Raku automation framework

Scc is a sparrow plugin that could be run over terminal to check security best practice of your Linux conf files :

• sshd
• sudoers
• bind
• redis
• sysctl

more services are coming , check it out and let me know what you think https://github.com/melezhik/sparrow-plugins/tree/master/scc

Dead simple ci is yamless pipeline engine for gitea/forgejo (using web hooks mechanism). Allowing one to write pipeline in general programming language. DSCI provides SDK allow to write extensions for the engine, the same way using general programming languages . This is an introduction - https://deadsimpleci.sparrowhub.io/doc/bash-plugins with simple examples on Bash and Python, but enough to get started ...

Introduction into Dead Simple CI framework for ci pipelines automation.

https://dev.to/melezhik/dead-simple-ci-introduction-1jh6

Hey everyone! After week of work finally rewrote dsci runner on golang.

git clone https://github.com/melezhik/dsci-runner.git cd dsci-runner go mod tidy go build -o dsci_runner main.go ./dsci_runner

That means just a single binary install Check it out ! )

Forgejo integrations details are here - http://deadsimpleci.sparrowhub.io/doc/forgejo-setup

Hey everyone! After week of work finally rewrote dsci runner on golang.

git clone https://github.com/melezhik/dsci-runner.git cd dsci-runner go mod tidy go build -o dsci_runner main.go ./dsci_runner

That means just a single binary install Check it out ! )

Forgejo integrations details are here - http://deadsimpleci.sparrowhub.io/doc/forgejo-setup

Hey! I am building a brand new CI based on top of forgejo/gitea - the thing is to use general purpose programming languages instead of YAML for pipelines. So I have launched a forgejo instance with DSCI runner integrated, where you can find some example pipelines for demo projects - http://forgejo.sparrowhub.io/root

So I am looking for beta testers, anyone who wants to try out the dsci - please let me know - so I will create an account for you ( you may find the link to the discord channel at the web site ) and you will start to create and run pipelines for projects you like

Dead simple CI - http://deadsimpleci.sparrowhub.io/ could be thought as an extension to any modern CI system - GitHub/Gitea/Gitlab/Forgejo/you name it , adding to default pipeline mechanism (usually based on yaml) the convenient for programmers use of general programming languages, it uses web hooks and commit statues API to report results back to native CI

Double TAP is lightweight testing framework where users write black box tests as rules checking output from tested "boxes". Boxes could be anything from http client, web server to messages in syslog. This universal approach allows to test anything with just dropping text rules describing system behavior in black box manner.

Rules are written in formal DSL and could be extended on many programming languages

Tool aims to help with infrastructure audit and testing as well as with validating development environments

Nice screenshots are attached )

Tomtit is a cli task runner when you need to run repetitive tasks / tools around your project. It's similar to make, but with more generic approach, not exactly tied to build tasks only

After one Rakulang community member and bio informatics developer mentioned the Nexflow data pipeline framework, I was surprised that Sparky and Sparrow6 eco system could be a good fit for such a type of tasks ...

Just create a .env/vars.env file which is not kept in source code, define some Bash variables here with sensitive data and then run sparrowdo cli referencing those variables in this file in a safe way:

—tags password=.env[PASSWORD],token=.env[TOKEN]

• variables are not exposed in bash history
• not seen via ps aux
• variables file gets transferred to remote host over scp
• file with variables not kept on remote host ( immediately removed after exporting to Sparrowdo scenario )
• host specific vs default env variables allowed

Safe and simple