Patrick Schratz

Some rpkgs.com news: - New website with a dynamic Arch/OS selector - cran.rpkgs.com got hardened as a dynamic/agnostic repository URL that works for all supported OS+Version combinations rpkgs.com supports and ... #rstats

Crow CI v5.5.0 is out Pipelines can now be written in Jsonnet alongside YAML, and logs can be stored on any S3-compatible backend. The admin panel gained automatic Docker cleanup for orphaned containers and networks, and trusted PRs can be permanently approved to skip the gate. (1/2)

Just released v5 of #crowci - a hard-fork of #woodpecker Many hours of work went into this new release, which looks and (almost) feels like an entirely new application! Besides a fully refactored UI, docs were migrated to #astro #starlight (crowci.dev).

- Global cron/secrets/registry views - Autoscaler UI integration - New metrics panel with both table and charts view - Support for multiple UI themes - Auto-follow steps within a workflow as they proceed - Conditions within "Deployment" runs (environment, task) actually take effect now

Just released v5 of #crowci - a hard-fork of #woodpecker Many hours of work went into this new release, which looks and (almost) feels like an entirely new application! Besides a fully refactored UI, docs were migrated to #astro #starlight (crowci.dev).

PSA: #rstats Posit PM binaries for spatial packages (sf, terra, etc.) on RHEL9/Rocky9/Alma9 are broken right now after a major bump from Proj8 to Proj9 in the Appstream repo lately. (1/2)

#cve #security I need advice in how to act in the following case: A medium-big software vendor using #golang claims that the reported CVEs by #trivy and MS defender on their statically linked binaries are false-positives. Only #snyk would give a "correct" result.

They are not willing to share their go.mod file to verify they are not using package version XY in them. I am somewhat skeptical about this argument. What are my best chances to find a verifiable proof to this (other than attempting to exploit the vuln?)

Deployed #harbor container registry lately. While it has a lot of features and it is great to have a self-hostable alternative to the big SaaS options, the lack of love for details, especially in the UI, is somewhat insane.

Version 3.7.0 of #crowci is released! > Crow CI is a Continuous Integration & Continuous Delivery (CI/CD)1 application. It is designed to be lightweight, simple to use and fast. crowci.dev #foss #cicd #codeberg

Trying for weeks to find a name for a new project incl. a com domain. Almost impossible these days, many domains are parked without being used. Likely in the hope to be sold to some that start with a large budget 🫠 ICANN should enforce the use within time X or drop the ownership again, IMO.

TIL: one can define dedicated connections for read and write operations for DBs. This allows distributing read-only queries among all replicas. Prob. late to the game but a game changer for traffic handling in (my) apps. #postgres #db #golang

I've released the first version of Crow CI (crowci.dev) yesterday (hosted on Codeberg (codeberg.org/crowci/crow). Crow is a fork of Woodpecker CI, which itself is a fork of Drone CI. #foss #cicd #codeberg #golang 🧵️

If you're running Woodpecker already, please check the migration notes in the 3.2.0 release beforehand. The public instance of Crow CI itself can be found at ci.crowci.dev/repos/1.

I've released the first version of Crow CI (crowci.dev) yesterday (hosted on Codeberg (codeberg.org/crowci/crow). Crow is a fork of Woodpecker CI, which itself is a fork of Drone CI. #foss #cicd #codeberg #golang 🧵️

Crow shines due to being forge-agnostic, i.e. it can be used together with GH, GL, BB, Gitea, and Forgejo in the same way. It is written in Go with a Vue frontend, and needs only ~ 150 MB in runtime. It works with Docker and Kubernetes (Podman not yet) and also comes with an optional autoscaler.