<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Offline on Robotmk</title><link>https://www.robotmk.org/en/tags/offline/</link><description>Recent content in Offline on Robotmk</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Sun, 26 Apr 2026 16:02:59 +0200</lastBuildDate><atom:link href="https://www.robotmk.org/en/tags/offline/index.xml" rel="self" type="application/rss+xml"/><item><title>Robotmk and RCC-Environments in air-gapped environments</title><link>https://www.robotmk.org/en/blog/rcc-envoffline/</link><pubDate>Sun, 26 Apr 2026 16:02:59 +0200</pubDate><guid>https://www.robotmk.org/en/blog/rcc-envoffline/</guid><description>&lt;p>RCC was one of the game changers with the introduction of Robotmk V2 - it takes care of the entire lifecycle of the Python environments that Robot Framework needs.&lt;/p>
&lt;p>That&amp;rsquo;s super convenient, but there&amp;rsquo;s a catch: RCC assumes that the test host has access to the internet to download the required packages.
This article describes a very practical way to use it in &lt;strong>isolated&lt;/strong> environments.&lt;/p></description></item></channel></rss>