In very special occasion during development, you may use directly a branch (e.g. master branch: https://lab.nexedi.com/nexedi/slapos/raw/master/software/theia/software.cfg) but this is not recommended.
Upload SR into Shacache (RapidSpace specific)
In order to have faster installation of software releases, you can upload SR in binary shacache (by using upload configuration in [shacache] section of your slapos configuration file). Then, if you configure your machines to download binaries from shacache, the machines will download the SR instead of compile it. You can even force some machine to only download from shacache and never compile.
For example, at RapidSpace, we configured 7 machines in vifib-test-agent account to upload binaries into shacache:
- Debian 8 (COMP-2537)
- Debian 9 (COMP-2825)
- Debian 10 (COMP-3102)
- Debian 11 (COMP-3487)
- Ubuntu 20.04 (COMP-3702)
- Ubuntu 22.04 (COMP-3823)
- Debian 11 raspberry (arm 64 bits) (COMP-3525)
- Debian 11 olimex (arm 32 bits) (COMP-3526)
slapos-client-vifib-test-agent.cfg configured on one of your SlapOS node, then supply the SR to the vifib-test-agent machines by:
$ for c in COMP-2537 COMP-2825 COMP-3102 COMP-3487 COMP-3702; do slapos supply --cfg ~/slapos-vifib-test-agent/slapos-client-vifib-test-agent.cfg https://lab.nexedi.com/nexedi/slapos/raw/1.0.299/software/theia/software.cfg $c ; done