<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/rss/styles.xsl" type="text/xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>devXY Blog</title><description>News, stories, and changelogs around Data Science and DevOps</description><link>https://devxy.io/</link><atom:link href="https://devxy.io/rss.xml" rel="self" type="application/rss+xml"/><item><title>CRAN R package binaries for Linux</title><link>https://devxy.io/blog/cran-r-package-binaries-launch/</link><guid isPermaLink="true">https://devxy.io/blog/cran-r-package-binaries-launch/</guid><description>Custom R repositories that offer R package binaries for a variety of Linux distributions (including Alpine Linux) and architectures.</description><pubDate>Tue, 24 Dec 2024 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;R community - it is time for something new: CRAN package binaries for Linux &lt;code&gt;arm64&lt;/code&gt; AND Alpine Linux!&lt;/p&gt;
&lt;p&gt;tl;dr:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;install.packages(&quot;vctrs&quot;, repos = &quot;https://cran.rpkgs.com/arm64/noble/latest&quot;)
install.packages(&quot;stringi&quot;, repos = &quot;https://cran.rpkgs.com/amd64/alpine321/latest&quot;)

# and more...
# find all identifiers at &amp;lt;https://www.devxy.io/r-package-binaries/&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;pre&gt;&lt;code&gt;# container examples
docker run --rm -it devxygmbh/r-ubuntu:4-noble R -q -e &apos;install.packages(&quot;vctrs&quot;); library(vctrs)&apos;
docker run --rm -it devxygmbh/r-alpine:4-3.21 R -q -e &apos;install.packages(&quot;stringi&quot;); library(stringi)&apos;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&amp;lt;div style=&quot;padding:59.12% 0 0 0;position:relative;&quot;&amp;gt;&amp;lt;iframe src=&quot;https://player.vimeo.com/video/1035389676?badge=0&amp;amp;autopause=0&amp;amp;player_id=0&amp;amp;app_id=58479&quot; frameborder=&quot;0&quot; allow=&quot;autoplay; fullscreen; picture-in-picture; clipboard-write&quot; style=&quot;position:absolute;top:0;left:0;width:100%;height:100%;&quot; title=&quot;Alpine package binaries: Install tidyverse&quot;&amp;gt;&amp;lt;/iframe&amp;gt;&amp;lt;/div&amp;gt;&amp;lt;script src=&quot;https://player.vimeo.com/api/player.js&quot;&amp;gt;&amp;lt;/script&amp;gt;&lt;/p&gt;
&lt;h2&gt;Historic background&lt;/h2&gt;
&lt;p&gt;As an R user for over ten years, I’ve always missed having binaries available for Linux.
In summer 2020, Posit began building amd64 binaries and with that providing an important asset to the R community.
This allowed people to install large numbers of packages in a fraction of the time, and CI/CD runs were finally completing in a few minutes.&lt;/p&gt;
&lt;p&gt;With the growing rise of centralized data science environments running in the cloud on Linux in the early 2020s, the need for binaries became imminent.
Previously, since R was mainly used on desktops, most users were satisfied with binaries for Windows and Mac only.
However, to succeed with their server-based offerings—Workbench and Connect—Posit (formerly RStudio) had to provide a solution for Linux environments.
Without binaries, these applications would have been practically unusable due to the long waiting times for R package installations.
Therefore, it made a lot of sense for Posit to tackle this field, paving the way for a new era of using R on (remote) Linux systems.&lt;/p&gt;
&lt;h2&gt;CRAN and the community&lt;/h2&gt;
&lt;p&gt;CRAN has long provided binaries for Windows and Mac—well before I started using R—and in 2020, it also delivered binaries for the arm64-based Apple Silicon architecture.
However, no effort was made to build Linux binaries at the time.
Given Posit’s initiatives in this area, there was little need for CRAN to take on the significant workload themselves.&lt;/p&gt;
&lt;p&gt;Admittedly, building Linux binaries is a complex task.
The diversity of Linux distributions, each with its own compilers and toolchains, means binaries must be tailored to these environments.
Major upgrades to these distributions periodically require a complete rebuild of all binaries.
Adding to the challenge, many system libraries required by R packages are not universally available across distributions.
All of this translates into substantial demands for both storage and computing resources.&lt;/p&gt;
&lt;p&gt;While Posit’s R package binaries were warmly welcomed by the community, the community itself was far from passive.
In fact, efforts to build Linux binaries predated Posit’s involvement, as highlighted in the CRAN documentation for Ubuntu binaries (https://cran.r-project.org/bin/linux/ubuntu/fullREADME.html).
Additionally, the &lt;code&gt;r2u&lt;/code&gt; package has provided Debian-specific binaries for a subset of R packages for many years.&lt;/p&gt;
&lt;p&gt;However, these earlier approaches have/had limitations.
The scope of available binaries was often narrow, and methods that relied on system package binaries posed challenges in shared environments where most users usually lack administrative privileges.
Relying on a single administrator to install or update R packages is not a practical or scalable solution for most environments.&lt;/p&gt;
&lt;p&gt;Next, the &lt;a href=&quot;https://github.com/cran4linux/bspm/&quot;&gt;bspm&lt;/a&gt; project was created, following a similar approach to those previously mentioned by leveraging the system’s native package manager and building a bridge to the Posit Package Manager.
However, it suffers from the same limitation outlined earlier.&lt;/p&gt;
&lt;p&gt;The most recent effort, &lt;a href=&quot;https://r-universe.dev/search&quot;&gt;R-universe&lt;/a&gt;, aims to build binaries for Windows, Mac, and Linux (amd64) using GitHub Actions.
This approach is the closest to a fully community-driven initiative conducted openly and is led by &lt;a href=&quot;https://github.com/jeroen&quot;&gt;Jeroen Ooms&lt;/a&gt;, a well-known and highly skilled member of the R community.&lt;/p&gt;
&lt;p&gt;However, all of the above are missing out on two points:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;arm64&lt;/code&gt; architecture&lt;/li&gt;
&lt;li&gt;Alpine Linux&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Why the arm64 architecture and Alpine Linux are important&lt;/h2&gt;
&lt;p&gt;Yes, &lt;code&gt;amd64&lt;/code&gt; binaries from sources like Posit, R-universe, or others are incredibly useful.
However, data science environments and CI/CD builds are increasingly shifting towards arm64-based servers.
These servers offer comparable performance with greater energy efficiency and are significantly more cost-effective—often up to 30% cheaper—when rented in the cloud compared to &lt;code&gt;amd64&lt;/code&gt; instances.&lt;/p&gt;
&lt;p&gt;Alpine Linux is a lightweight Linux distribution optimized for size, primarily used in containerized CI/CD tasks.
Its images are typically 2-5 times smaller than those built on other popular distributions like Ubuntu or Red Hat.
However, Alpine differs significantly from other distributions in one key aspect: it uses the MUSL C library instead of the more common GLIBC.&lt;/p&gt;
&lt;p&gt;This distinction introduces complications for C and C++ code, requiring specific adaptations for compatibility with MUSL. Currently, CRAN does not enforce checks for MUSL-based distributions, and the lack of prebuilt binaries means most package authors don’t address these compatibility issues.
As a result, a significant portion of R packages with C bindings cannot be installed on Alpine.&lt;/p&gt;
&lt;p&gt;Nevertheless, encouraging package authors to add MUSL support is a necessary first step.
Once a substantial number of packages are compatible, Alpine could become a viable option for R-based CI/CD workflows.
This shift might, in turn, encourage broader adoption, motivating users to prioritize MUSL compatibility in their packages and further expanding Alpine’s utility in the R ecosystem.&lt;/p&gt;
&lt;p&gt;After building all CRAN packages for Alpine for the first time, the results were surprisingly positive: out of 21,7xx packages, 21,502 (99.1%) successfully built for &lt;code&gt;amd64&lt;/code&gt;, and 20,405 (94.1%) for &lt;code&gt;arm64&lt;/code&gt;.
Detailed and up-to-date build statistics are available on the &lt;a href=&quot;https://app.devxy.io&quot;&gt;&quot;R package binaries dashboard&quot;&lt;/a&gt;.
While not all build failures are directly attributable to MUSL/GLIBC compatibility issues, many likely are.
It now falls to the authors and the community to investigate these failures, report the issues, and work towards fixing them.&lt;/p&gt;
&lt;h2&gt;Why also binaries for amd64?&lt;/h2&gt;
&lt;p&gt;Good question.
Initially, only arm64 binaries were in scope.
However, I quickly realized that I would need to change the main URL every time when working in a multi-arch R environment, i.e. to Posits Package Manager for amd64 and to cran.devxy.io for arm64.
This becomes annoying quickly, let alone thinking about it.&lt;/p&gt;
&lt;p&gt;I realized that users should be able to use the same repository URL for any architecture including dynamic arch identifiers for the respective one at hand.
Ideally, the arch identifier should be settable in a dynamic way, e.g. via &lt;code&gt;$(arch)&lt;/code&gt;.
Unfortunately, there are multiple ways to refer to a specific architecture: &lt;code&gt;amd64&lt;/code&gt; &amp;amp; &lt;code&gt;x86_64&lt;/code&gt; and &lt;code&gt;arm64&lt;/code&gt; &amp;amp; &lt;code&gt;aarch64&lt;/code&gt;.
I went for the first options for both, i.e. &lt;code&gt;amd64&lt;/code&gt; and &lt;code&gt;arm64&lt;/code&gt;.&lt;/p&gt;
&lt;h2&gt;Sustainability and costs&lt;/h2&gt;
&lt;p&gt;While many parts are automated and publicly available in the &lt;a href=&quot;https://codefloe.com/rpkgs&quot;&gt;rpkgs&lt;/a&gt; organization, keeping everything up-to-date so that users can rely on the service is an ambitious undertaking.
Yet I am keen to take it on and believe that it is possible if the community contributes to the project by investigating build failures of missing packages, contributing to the costs of the service (hosting, rebuilds, etc.) and improving the build chain.
I&apos;ve always wanted such a project to exist rather than having to rely on a closed build system nobody can interact with.&lt;/p&gt;
&lt;p&gt;That being said: let&apos;s talk about costs.
Building binaries, storing them and distributing them incurs costs.
So far, I am paying for all of these with my personal money.
Me? Yes, me.
While it is hosted under the umbrella of devXY, a Ltd., it is a one-person company at the time of writing this, operating effectively using my personal money.&lt;/p&gt;
&lt;p&gt;As said earlier, building this has been a personal wish of mine and I am also fully OK paying for it and giving back to the community.
While the building part costs will stay static for the most, the storage and bandwidth costs will steadily increase.
Especially the latter has potential to grow really large, depending on how many people will use it.
Therefore, I have to set a limit on the provided bandwidth to avoid abuse and keep cost under control.
This limit has been set to 50 TB per month for the start.
I am happy to increase it once costs are covered by the community.
While this might look restrictive at first, especially compared to Posit providing binaries without any limits, devXY can just not compete with a company of Posits size.&lt;/p&gt;
&lt;p&gt;At the same time I would like to ask medium/large companies planning to use the service to reach out to me and ask for a private URL (for a monthly fee).
The main URL cran.devxy.io is &lt;strong&gt;aimed for the community&lt;/strong&gt;, for developers and other individuals.
With reasonable usage of individuals, 50 TB can be a lot - at the same time, this can be a low volume if a large company jumps on it and uses it for hundreds of (daily) CI/CD jobs.&lt;/p&gt;
&lt;h2&gt;Signoff&lt;/h2&gt;
&lt;p&gt;This post is an entry post, outling the current state and motivation for the overall project.
A separate post will provide more technical details and explain how all of this could be built by a single person with a limited budget.&lt;/p&gt;
</content:encoded><category>r</category></item><item><title>ForgeGo: a mobile client for Forgejo</title><link>https://devxy.io/blog/forgego-release/</link><guid isPermaLink="true">https://devxy.io/blog/forgego-release/</guid><description>ForgeGo, our mobile client for Forgejo, is now available on the App Store and Google Play.</description><pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;ForgeGo, a mobile client for &lt;a href=&quot;https://forgejo.org&quot;&gt;Forgejo&lt;/a&gt;, is now available for iOS and Android.&lt;/p&gt;
&lt;p&gt;&amp;lt;div style=&quot;display: flex; flex-wrap: wrap; align-items: center; justify-content: center; gap: 12px 20px; padding: 12px 0&quot;&amp;gt;
&amp;lt;a href=&quot;https://apps.apple.com/app/forgego/id6775529949&quot;&amp;gt;&amp;lt;img src=&quot;/blog-images/badges/app-store.svg&quot; alt=&quot;Download on the App Store&quot; style=&quot;display: block; height: 48px; width: auto; margin: 0&quot; /&amp;gt;&amp;lt;/a&amp;gt;
&amp;lt;a href=&quot;https://play.google.com/store/apps/details?id=io.devxy.forgego&quot; style=&quot;margin: -12px&quot;&amp;gt;&amp;lt;img src=&quot;/blog-images/badges/google-play.png&quot; alt=&quot;Get it on Google Play&quot; style=&quot;display: block; height: 72px; width: auto; margin: 0&quot; /&amp;gt;&amp;lt;/a&amp;gt;
&amp;lt;/div&amp;gt;&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../../assets/img/forgego-screens.jpg&quot; alt=&quot;ForgeGo on iOS: the home screen across all servers, an issue list, and a repository&apos;s files&quot; /&gt;&lt;/p&gt;
&lt;h2&gt;Why we built it&lt;/h2&gt;
&lt;p&gt;Most of our work lives on Forgejo instances, spread across a few servers and accounts.
A lot of what happens there does not need a laptop: reading an issue, answering a comment, checking whether CI passed, looking at a diff before merging.
We wanted an app for this that handles several servers at once.
So we built one.&lt;/p&gt;
&lt;h2&gt;What it does&lt;/h2&gt;
&lt;p&gt;ForgeGo covers the parts of Forgejo you are likely to use while being on the go:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;repositories, files, branches and releases&lt;/li&gt;
&lt;li&gt;issues and pull requests: read diffs and reviews, comment, and merge&lt;/li&gt;
&lt;li&gt;CI status from Forgejo Actions and external CI&lt;/li&gt;
&lt;li&gt;notifications&lt;/li&gt;
&lt;li&gt;search across repositories, issues, pull requests and users&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Because we use so many instances across servers where we administrate multiple accounts, an efficient multi-server and multi-account approach was very important to us.&lt;/p&gt;
&lt;p&gt;&amp;lt;img src=&quot;/blog-images/forgego-switcher.gif&quot; width=&quot;360&quot; style=&quot;display: block; margin: 0 auto&quot; alt=&quot;Switching between a codefloe.com and a git.devxy.io account from the home screen&quot; /&amp;gt;&lt;/p&gt;
&lt;h2&gt;How it works&lt;/h2&gt;
&lt;p&gt;The app talks to the Forgejo servers directly through their REST API.
There is no ForgeGo backend in between.
Access tokens stay in the device keychain or keystore.
The app contains no analytics or advertising SDK.&lt;/p&gt;
&lt;p&gt;ForgeGo requires Forgejo 16.0 or newer.&lt;/p&gt;
&lt;h2&gt;Free and Pro&lt;/h2&gt;
&lt;p&gt;The app is free to use for everyday work with Forgejo.
A Pro subscription adds a few things on top: a unified view that merges all servers and accounts into one list, background notifications, SSH terminals for repositories, and no limits on favourites and search history.&lt;/p&gt;
&lt;p&gt;The unified view is really powerful: you can manage all your repos and notifications in one view and easily select which account you want to use for an action.
Once set up, it is really a game changer on the go!&lt;/p&gt;
</content:encoded><category>forgejo</category></item><item><title>TLS Docker jobs with Forgejo Actions (systemd)</title><link>https://devxy.io/blog/forgejo-runner-dind/</link><guid isPermaLink="true">https://devxy.io/blog/forgejo-runner-dind/</guid><description>A guide to configuring TLS-enabled Docker-in-Docker (DIND) containers with Forgejo runner running via systemd, including certificate mounting and secure job isolation.</description><pubDate>Fri, 31 Oct 2025 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;While Forgejo runner (FJ) runs jobs and actions with a container in most cases, running container-based jobs within such is quite tricky.
Especially when aiming for TLS-support in docker[^1] combined with FJ runner running via &lt;code&gt;systemd&lt;/code&gt; on the host.
This combination requires mounting the DIND TLS certs into various places across nested environments.&lt;/p&gt;
&lt;p&gt;A &lt;a href=&quot;https://forgejo.org/docs/latest/admin/actions/docker-access/&quot;&gt;dedicated Forgejo documentation page&lt;/a&gt; about using docker with Forgejo runner exists, though at the time of writing this article, it did not yet cover TLS support.
Additionally, another example showcasing a TLS-supported setup with FJ runner running in a container exists &lt;a href=&quot;https://code.forgejo.org/forgejo/runner/src/branch/main/examples/docker-compose&quot;&gt;here&lt;/a&gt;.
While these were helpful throughout the configuration process (including a conversation with the always helpful &lt;a href=&quot;https://codeberg.org/viceice&quot;&gt;@viceice&lt;/a&gt;), they did not cover all the details needed to make this setup work.&lt;/p&gt;
&lt;p&gt;This post aims at closing this gap and saving others some time when going down the same path.&lt;/p&gt;
&lt;p&gt;::: tip
To install Forgejo runner, we use our &lt;code&gt;forgejo_runner&lt;/code&gt; role in the &lt;a href=&quot;https://galaxy.ansible.com/ui/repo/published/devxy/cicd/content/&quot;&gt;&lt;code&gt;devxy.cicd&lt;/code&gt; Ansible Collection&lt;/a&gt;.
:::&lt;/p&gt;
&lt;h2&gt;1. Create a DIND container&lt;/h2&gt;
&lt;p&gt;There are two important points here:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The DIND container must run with TLS enabled on port 2367&lt;/li&gt;
&lt;li&gt;A valid hostname must be set which can be referenced later within the job container&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Here&apos;s an Ansible docker-compose definition for the DIND container:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;community.docker.docker_container:
  name: docker
  # this triggers dind to generate certs with this SAN entry
  hostname: dind_container
  image: docker:dind
  state: started
  restart_policy: always
  privileged: true
  env:
    DOCKER_TLS_CERTDIR: /certs
  volumes:
    - /mnt/docker_certs:/certs
  ports:
    - &quot;127.0.0.1:2376:2376&quot;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;::: note
Regarding the use of a bind mount instead of a volume mount for the &lt;code&gt;/certs&lt;/code&gt; directory: a bind mount caused access issues when starting the FJ runner because the runner is running as the &lt;code&gt;forgejo_runner&lt;/code&gt; user while the mount is owned by &lt;code&gt;root&lt;/code&gt;.
:::&lt;/p&gt;
&lt;h2&gt;2. Connect &lt;code&gt;systemd&lt;/code&gt; FJ runner to DIND daemon&lt;/h2&gt;
&lt;p&gt;The idea is to run all jobs via the DIND container and not via the host&apos;s docker daemon.
This provides a secure and isolated environment for running jobs.
Otherwise the host docker daemon would need to be used, which would result in container jobs being able to possibly access the host filesystem or network.&lt;/p&gt;
&lt;p&gt;We need to set some env vars in the service file to tell Forgejo runner to talk to the DIND daemon using TLS.
Also we need to tell it where to find the TLS certs.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Environment=&quot;DOCKER_TLS_VERIFY=1&quot;
Environment=&quot;DOCKER_CERT_PATH=/mnt/docker_certs/client&quot;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The &lt;code&gt;/mnt/docker_certs/client&lt;/code&gt; mount contains the TLS certs from the DIND container which are needed to connect to the DIND daemon (see also the diagram below for a graphical representation).&lt;/p&gt;
&lt;p&gt;With this setting, all containers will be started within the DIND container - hence you will not see them on the host anymore via &lt;code&gt;docker ps&lt;/code&gt;.&lt;/p&gt;
&lt;h2&gt;3. Mounting DIND TLS certs into the job containers&lt;/h2&gt;
&lt;p&gt;Now when a new container job starts, a child container is spawned for each.
These containers must also have the DIND TLS certs available.&lt;/p&gt;
&lt;p&gt;In addition, the &lt;code&gt;DOCKER_HOST&lt;/code&gt; env var must be set so the job containers know where to find the docker daemon.
But now comes the tricky part: while it was possible to use a (direct) bind mount for the DIND container and FJ runner via the host filesystem, care must be taken now with respect to source and destination as the job containers are nested inside the DIND container!&lt;/p&gt;
&lt;p&gt;This means that from the PoV of the job containers, the &quot;host&quot; is the DIND container itself.
Our goal is to mount the DIND TLS certs which live under &lt;code&gt;/certs&lt;/code&gt;.
The solution is a bind mount between the DIND container and the job container using &lt;code&gt;/certs:/certs&lt;/code&gt;.
This can be achieved by adding &lt;code&gt;&quot;--volume /certs:/certs:ro&quot;&lt;/code&gt; to the &lt;code&gt;container.options&lt;/code&gt; setting in the FJ runner config file.&lt;/p&gt;
&lt;p&gt;To verify this approach, we can start a build, let it &quot;sleep&quot;, exec into the DIND container and from there exec into the job container. There we should find the following in &lt;code&gt;/certs&lt;/code&gt;:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;tree certs/

certs/
├── ca
│   ├── cert.pem
│   ├── cert.srl
│   └── key.pem
├── client
│   ├── ca.pem
│   ├── cert.pem
│   ├── csr.pem
│   ├── key.pem
│   └── openssl.cnf
└── server
    ├── ca.pem
    ├── cert.pem
    ├── csr.pem
    ├── key.pem
    └── openssl.cnf
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;🎉️&lt;/p&gt;
&lt;h2&gt;4. Telling the job containers about the Docker daemon&lt;/h2&gt;
&lt;p&gt;Last step: after mounting the TLS certs, we need to tell the job containers where to find the docker daemon.
We can do so via an env var &lt;code&gt;DOCKER_HOST=tcp://dind_container:2376&lt;/code&gt; coupled with &lt;code&gt;DOCKER_TLS_VERIFY=1&lt;/code&gt; and &lt;code&gt;DOCKER_CERT_PATH=/certs/client&lt;/code&gt;.
These can be set in the &lt;code&gt;runner.envs&lt;/code&gt; section in the FJ runner config.&lt;/p&gt;
&lt;p&gt;And now the last bit: by default, the job containers are not able to resolve this hostname properly.
To enable this, we need to add &lt;code&gt;--add-host=dind_container:host-gateway&lt;/code&gt; to &lt;code&gt;container.options&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;That&apos;s it! 😅️&lt;/p&gt;
&lt;h2&gt;Architecture&lt;/h2&gt;
&lt;p&gt;As the wiring got somewhat complex, I&apos;ve put together a diagram to illustrate the architecture:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;../../assets/img/forgejo-runner-architecture.png&quot; alt=&quot;Architecture Diagram&quot; /&gt;&lt;/p&gt;
&lt;p&gt;[^1]: Docker has been pushing for TLS-backed connections for some time and will remove non-TLS connections soon.
While this has been announced several major versions ago, it will (really) happen at some point, so putting the effort in is worth it.
TLS-backed connections means that clients connecting to the Docker daemon will need to authenticate using TLS certificates.
These certificates are generated by the DIND daemon during startup and must be provided by clients during the connection process.&lt;/p&gt;
</content:encoded><category>sys-admin</category><category>forgejo</category><category>ansible</category></item><item><title>Compiling HAProxy with WolfSSL</title><link>https://devxy.io/blog/haproxy-with-wolfssl/</link><guid isPermaLink="true">https://devxy.io/blog/haproxy-with-wolfssl/</guid><description>A guide to compiling HAProxy with WolfSSL for enhanced performance and HTTP/3 support, including detailed build instructions.</description><pubDate>Fri, 16 May 2025 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;After reading the recent blog post of the HAProxy team on &lt;a href=&quot;https://www.haproxy.com/blog/state-of-ssl-stacks&quot;&gt;&quot;The State of SSL Stacks&quot;&lt;/a&gt;, we got convinced to move away from OpenSSL and try out one of their competitors for substantially enhanced performance.&lt;/p&gt;
&lt;p&gt;To be able to use HTTP/3 with HAProxy these days, HAProxy must be compiled from source with a Quic-enabled SSL library.&lt;/p&gt;
&lt;p&gt;The following snippet might be helpful for some which aim for the same migration to save time on finding the right flags for each library.
Note: Don&apos;t forget to install the required build tools on your respective distribution (we used Almalinux 9.5).&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;# clone WolfSSL
git clone --depth 1 --branch v5.8.0-stable https://github.com/wolfssl/wolfssl.git /tmp/wolfssl

# build WolfSSL
cd /tmp/wolfssl
./autogen.sh
./configure TARGET=linux-glibc --enable-quic --enable-tls13 --enable-alpn --enable-haproxy --prefix=/opt/wolfssl --libdir=/opt/wolfssl/lib
make -j$(nproc)
make install

# clone HAProxy
git clone --depth 1 --branch v3.1.7 https://git.haproxy.org/git/haproxy-3.1.git /tmp/haproxy

# build HAProxy
cd /tmp/haproxy
make TARGET=linux-glibc USE_OPENSSL_WOLFSSL=1 USE_QUIC=1 USE_PROMEX=1 USE_LIBCRYPT=1 SSL_LIB=/opt/wolfssl/lib  SSL_INC=/opt/wolfssl/include
make install
&lt;/code&gt;&lt;/pre&gt;
&lt;pre&gt;&lt;code&gt;haproxy -vv

HAProxy version 3.1.7 2025/04/17 - https://haproxy.org/
Status: stable branch - will stop receiving fixes around Q1 2026.
Known bugs: http://www.haproxy.org/bugs/bugs-3.1.7.html
Running on: Linux 5.14.0-503.40.1.el9_5.aarch64 #1 SMP PREEMPT_DYNAMIC Mon May 5 05:57:36 EDT 2025 aarch64
Build options :
  TARGET  = linux-glibc
  CC      = cc
  CFLAGS  = -O2 -g -fwrapv
  OPTIONS = USE_LIBCRYPT=1 USE_OPENSSL_WOLFSSL=1 USE_QUIC=1 USE_PROMEX=1
  DEBUG   =

Feature list : -51DEGREES +ACCEPT4 +BACKTRACE -CLOSEFROM +CPU_AFFINITY +CRYPT_H -DEVICEATLAS +DL -ENGINE +EPOLL -EVPORTS +GETADDRINFO -KQUEUE -LIBATOMIC +LIBCRYPT +LINUX_CAP +LINUX_SPLICE +LINUX_TPROXY -LUA -MATH -MEMORY_PROFILING +NETFILTER +NS -OBSOLETE_LINKER +OPENSSL -OPENSSL_AWSLC +OPENSSL_WOLFSSL -OT -PCRE -PCRE2 -PCRE2_JIT -PCRE_JIT +POLL +PRCTL -PROCCTL +PROMEX -PTHREAD_EMULATION +QUIC -QUIC_OPENSSL_COMPAT +RT +SHM_OPEN +SLZ +SSL -STATIC_PCRE -STATIC_PCRE2 +TFO +THREAD +THREAD_DUMP +TPROXY -WURFL -ZLIB
&lt;/code&gt;&lt;/pre&gt;
</content:encoded><category>sys-admin</category></item><item><title>devxy.data_science_core - Ansible Collection for Data Science tools</title><link>https://devxy.io/blog/intro-ansible-collection-for-data-science/</link><guid isPermaLink="true">https://devxy.io/blog/intro-ansible-collection-for-data-science/</guid><description>Introduction of devxy.data_science_core Ansible collection containing roles for R, Python and Quarto.</description><pubDate>Sat, 26 Oct 2024 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Automating the installation of Data Science tools helps to more efficiently deploy new versions as they come out and deprecate versions which are EOL.
The new Ansible collection &lt;code&gt;devxy.data_science_core&lt;/code&gt; aims to make such tasks even easier now: it provides Ansible roles for R, Python and Quarto which are packed with helpful workflows and smart defaults.&lt;/p&gt;
&lt;p&gt;The collection is published on &lt;a href=&quot;https://galaxy.ansible.com/ui/repo/published/devxy/data_science_core/&quot;&gt;Ansible Galaxy&lt;/a&gt; and can be installed via&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;ansible-galaxy collection install devxy.data_science_core
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;To use one of the roles in an Ansible playbook, do&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;- name: Install Quarto
  hosts: all
  become: true

  roles:
    - role: devxy.data_science_core.quarto
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;All variables are documented in detail in a tabular format thanks to &lt;a href=&quot;https://ansible-doctor.geekdocs.de/&quot;&gt;ansible-doctor&lt;/a&gt; (see for example the &lt;a href=&quot;https://codefloe.com/devxy/ansible-data-science-core/src/branch/main/roles/r/README.md&quot;&gt;README of the R role&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;If you face any issues or are missing a feature, open an issue at &lt;a href=&quot;https://codefloe.com/devxy/ansible-data-science-core/&quot;&gt;https://codefloe.com/devxy/ansible-data-science-core/&lt;/a&gt;.&lt;/p&gt;
</content:encoded><category>ansible</category><category>r</category><category>quarto</category></item></channel></rss>