rkd 2.0.0.0rc10.dev1

Task executor - balance between Makefile and Gradle.

Task executor - balance between Makefile and Gradle [see documentation], designed with :heart: by RiotKit for DevOps.

Stop writing hacks in Makefile, use Python snippets for advanced usage, for the rest use simple few lines of Bash, share code between your projects using Python Packages.

RKD can be used on PRODUCTION, for development, for testing, to replace some of Bash scripts inside docker containers, and for many more, where Makefile was used.

Example use cases

• Docker based production environment with multiple configuration files, procedures

• Database administrator workspace (importing dumps, creating new user accounts, plugging/unplugging databases)

• Development environment (executing migrations, importing test database, splitting tests and running parallel)

• On CI (prepare project to run on eg. Jenkins or Gitlab CI) - RKD is reproducible on local computer which makes inspection easier

• Kubernetes/OKD deployment workspace (create shared YAML parts with JINJA2 between multiple environments and deploy from RKD)

• Automate things like certificate regeneration on production server, RKD can generate any application configs using JINJA2

• Installers (RKD has built-in commands for replacing lines in files, modifying .env files)

Quick start

# 1) via PIP
pip install rkd

# 2) Create project (will create a virtual env and prepare files that could be commited to git)
rkd :rkd:create-structure

Please check available releases there: https://pypi.org/project/rkd/#history

Goals:

• Define tasks as simple as in Makefile

• Write tasks code in Python as simple as possible

• Reuse code as simple as in Gradle (using extensions that provides tasks. Extensions are installable from PIP)

• Simple configuration in Python

• Integrates with GIT

• Suitable for PRODUCTION (log as much as possible, log each executed task into separated *.log files). We planned also extended logging of most important auditing information such as who executed action, and how the state looked in that time

Rules

• No hooks eg. task.executeAfter(otherTask), no complex dependencies

• No in-memory state between tasks. State could be only changed in files/database/kv-store like it is in other build systems

• No dynamic tasks names eg. by turning on Publish component it should not create tasks eg. :publishIWAToDockerRegistry (where IWA is the project name)

• Don’t pack too many features into the core, do this in external modules. Keep the RKD core clean!

• Full static analysis, you can work on makefile.py and on task’s code in PyCharm with full code completion!

• Do early validation. Runtime validation for long running builds is a pain-in-the-ass for the user.

• Show clear error messages as much as it is possible. Task not found? Tell the user - do not leave a stack trace. Import error in makefile.py? Tell the user + add stack trace. RESPECT TIME OF ALL OF US! :)

• Do not overuse libraries in RKD core - it must be installable in any environment, including Docker. Libraries count should be small, and the libraries cannot depend on GCC/G++

RKD in action

YAML syntax example

Python syntax example (makefile.py)

Documentation

Please read the documentation here.

Roadmap

Check our github milestones, to see what’s actually planned for next releases.

Projects using RKD

• Taiga - automatic packaging into PRODUCTION docker image

• Taiga Events - automatic packaging into PRODUCTION docker image

• RiotKit Harbor (upcoming 2.0 version uses RKD) - Automated docker-compose PRODUCTION environment with Service Discovery, automatic SSL, rolling deployments and more!

• Harbor Simple Router - NGINX image with predefined templates, controlled by environment variables

• Kubernetes/OKD workspace - create deployments with reusable YAMLs

Alternative ways of installation

• Arch Linux AUR package made by ragouel

Releasing

1. git tag -s v1.0.0

2. Create a release in Github releases

3. Wait for pipeline to build and publish to PyPI

From authors

We are grassroot activists for social change, so we created RKD especially in mind for those fantastic initiatives:

• RiotKit (https://riotkit.org)

• International Workers Association (https://iwa-ait.org)

• Anarchistyczne FAQ (http://anarchizm.info) a translation of Anarchist FAQ (https://theanarchistlibrary.org/library/the-anarchist-faq-editorial-collective-an-anarchist-faq)

• Federacja Anarchistyczna (http://federacja-anarchistyczna.pl)

• Związek Syndykalistów Polski (https://zsp.net.pl) (Polish section of IWA-AIT)

• Komitet Obrony Praw Lokatorów (https://lokatorzy.info.pl)

• Solidarity Federation (https://solfed.org.uk)

• Priama Akcia (https://priamaakcia.sk)

Special thanks to Working Class History for very powerful samples that we could use in our unit tests.