Rcc

RCC

[](https://github.com/joshyorko/rcc/actions/workflows/rcc.yaml) [](https://github.com/joshyorko/rcc/actions/workflows/lint.yml) [](https://codecov.io/gh/joshyorko/rcc) [](https://github.com/joshyorko/rcc/releases)


RCC allows you to create, manage, and distribute Python-based self-contained automation packages. RCC also allows you to run your automations in isolated Python environments so they can still access the rest of your machine.

**Repeatable, Contained Code** - movable and isolated Python environments for your automation.

Together with [robot.yaml](https://robocorp.com/docs/robot-structure/robot-yaml-format) configuration file, `rcc` is a foundation that allows anyone to build and share automation easily.

RCC is actively maintained by [JoshYorko](https://github.com/joshyorko).

Why use rcc?

• You do not need to install Python on the target machine
• You can control exactly which version of Python your automation will run on (..and which pip version is used to resolve dependencies)
• You can avoid Works on my machine
• No need for venv, pyenv, ... tooling and knowledge sharing inside your team.
• Define dependencies in conda.yaml and automation config in robot.yaml and let RCC do the heavy lifting.
• If you have run into "dependency drifts", where once working runtime environment dependencies get updated and break your production system?, RCC can freeze ALL dependencies, pre-build environments, and more.
• RCC will give you a heads-up if your automations have been leaving behind processes after running.

...and much much more.

Getting Started

**Install rcc**

[Installation guide](#installing-rcc-from-