Since I announced a RICH - Rakudo Issues Confirmation Helper, I've been playing a lot with an automation of test cases for known Rakudo bugs.One thing I've found really interesting in this journey is how Sparrow could be a good fit to express issues through automation scenarios. While I am not pretending on substituting existing … Continue reading Chasing Rakudo bugs with Sparrow
Sparky is a lightweight CI server written on Raku. It uses Bailador for UI and Sparrow/Sparrowdo as an automation engine. Initially the server was written to be run on a single machine and did not scale well. So it only could handle a small/medium load, mostly working in localhost mode. Now, with the help of … Continue reading Sparky on k8s cluster
Rakudo releases could be tough. Because the language is still in very development stage. New issues arrive daily. Let's me introduce my attempt to help release managers and Rakudo developers to keep track of addressing existing issues with daily Rakudo commits. Enter a RIP service ( maybe I should choose a better name ? ) … Continue reading Rakudo Issues Player
Why yet another converter when pandoc and many others already do the job? Size. Pandoc uses TeX to generate PDFs. All the other converters I found use a Web browser in one way or another to make the PDF. Pandoc is 50 MB by itself, not counting TeX! In less than 1.2 MB (a 5.25″ floppy 😉 ) and a single file, pfft will do the job.
Of course, there is a catch: pfft uses Pango and Cairo to make the PDFs. Those have their own dependencies, but are installed on many Ubuntu systems by default! So pfft itself does not add to the dependency load those systems already carry.
(By the way, I use and appreciate both TeX and Pandoc. They are great tools! …
View original post 88 more words
I've recently launched an experimental service called RakuPlay. It allows users to run Raku code snippets against different version of Rakudos including Rakudo developers SHA commits.It also supports automatic Raku modules installation using Rakufile syntax.A common user page looks like that:Rakudo developer page allows to run a code against certain Rakudo commits:Once a user hit … Continue reading RakuPlay introduction
Sparrow is a Raku based automation tool comes with the idea of Sparrow plugins - small reusable pieces of code, runs as a command line or Raku function. Raku: my %state = task-run "say name", "name", %( bird => "Sparrow" ); say %state<name>; Cli: $ s6 --plg-run name@bird=Sparrow One can even create wrappers for existing … Continue reading Raku-Utils Proposal
"RakuOps series – an attempt to show people who write on Raku how to use the language in daily DevOps tasks – automation, configuration management, Docker containers and so on"It's been two weeks I've been playing with Sparrowdo - an automation tool written on Raku and based on Sparrow automation framework. Now it's a time … Continue reading RakuOps. Issue Number 2.
RakuOps series - an attempt to show people who write on Raku how to use the language in daily DevOps tasks - automation, configuration management, Docker containers building and so on.While I don't know for sure which topics will attract the community interest, I hope that during this series I'll get some feedback so I … Continue reading RakuOps. Issue 1.
A few days ago several discussions have been launched where people try to deal with managing none Raku / native dependencies for Raku modules. While a solution is far from being found or at least is complete here is my, Sparrow take on the problem. Raku-native-deps Raku-native-deps is a Sparrow plugin to parse META6.json file … Continue reading Managing External Raku Dependencies using Sparrow
Nowadays many Raku modules authors ship cli tools as a part of their Raku modules distributions.RakuDist provides a dead easy way to test those scripts. The benefit, it takes a minimal coding andfully integrated into RakuDist service. Cli application example Say, we have a script.raku shipped as a part of a Raku module. $ cat … Continue reading RakuDist – Dead Easy Way to Test Raku Cli Applications