Offline Installation and Upgrades

This guide is intended for the first time offline installation of RhodeCode Control, RhodeCode Enterprise and the VCS Server. If you are already in an offline environment and want to upgrade to the latest releases first see Upgrade RhodeCode Control.

Offline Steps

  1. Download the RhodeCode Control installer for your platform.
  2. Transfer the RhodeCode Control installer, package to the machine you’ll run the offline commands.
  3. Install RhodeCode Control on the offline machine.
  4. Run installation with –offline flag to show which file needs to be downloaded into cache storage, follow up with instructions on how to put the download files into the cache storage.
$ rccontrol install VCSServer --offline

Offline mode enabled. Using files from the local cache.

File /home/ubuntu/.rccontrol/cache/RhodeCodeVCSServer-4.6.1+x86_64-linux_build20170213_1900.tar.bz2 not found.
Please manually download file from the link below and store it inside /home/ubuntu/.rccontrol/cache directory.
https://dls.rhodecode.com/linux/RhodeCodeVCSServer-4.6.1+x86_64-linux_build20170213_1900.tar.bz2

$ rccontrol install Enterprise --offline

Offline mode enabled. Using files from the local cache.

File /home/ubuntu/.rccontrol/cache/RhodeCodeEnterprise-4.6.1+x86_64-linux_build20170213_1900.tar.bz2 not found.
Please manually download file from the link below and store it inside /home/ubuntu/.rccontrol/cache directory.
https://dls.rhodecode.com/linux/RhodeCodeEnterprise-4.6.1+x86_64-linux_build20170213_1900.tar.bz2

Note

For RhodeCode Enterprise 2.x you do not need a VCS Server. It is only required for 3.x and above.

  1. Run the appropriate commands again with --version and --offline. E.g.
 $ rccontrol install VCSServer --version 4.6.1 --offline

* See the examples below or :ref:`rcc-cli` for more details.

Important

If you do not specify the --version argument RhodeCode Control assumes the latest version which may not be in your cache and result in the command failing.

Be aware that failure may also be caused by placing packages into the cache that have the correct version but wrong system architecture!

Examples

Importing your existing older instance to be managed by RhodeCode Control.

$ rccontrol import Enterprise <path to INI> --version 2.2.7 --offline

Installing a VCS Server and RhodeCode Enterprise instance.

$ rccontrol install VCSServer --version 3.3.3 --offline
$ rccontrol install Enterprise --version 3.3.3 --offline

Upgrading an existing VCS Server and RhodeCode Enterprise instance.

$ rccontrol upgrade vcsserver-1 --version 4.3.3 --offline
$ rccontrol upgrade enterprise-1 --version 4.3.3 --offline