Updating Cloudbox (Master branch)

You can use this guide to keep up with new additions/changes with Cloudbox.

Foreword

• You will not lose your existing data (e.g. Plex libraries, Sonarr/Radarr db, configs, etc) as that is stored in /opt.

• The follow settings files will remain intact:

  • ansible.cfg
  • accounts.yml
  • settings.yml
  • adv_settings.yml
  • backup_config.yml
  • backup_excludes.txt (if it exists)

• Since Docker itself may be updated during this process, some non-Cloudbox docker containers may either get stopped or removed during this process, but their persistent config data should remain intact.

Update Cloudbox

1. Pull the latest changes to the repo.

   cd ~/cloudbox && git fetch && git reset --hard @{u}

   Among other things, this will show you the last commit message from the repo. That specific commit message is not germane to performing the update.

   For example, you'll see something like this [absolutely not exactly this]:

   ➜  cloudbox git:(master) cd ~/cloudbox && git fetch && git reset --hard @{u}
   remote: Enumerating objects: 22, done.
   remote: Counting objects: 100% (22/22), done.
   remote: Compressing objects: 100% (6/6), done.
   remote: Total 12 (delta 6), reused 9 (delta 4), pack-reused 0
   Unpacking objects: 100% (12/12), done.
   From https://github.com/cloudbox/cloudbox
      cf5b0bd8..e5763494  master     -> origin/master
      acc03830..9003e8cf  develop    -> origin/develop
   HEAD is now at 1234abcd Docs: placeholder message for wiki use

   The volume of output you see here will depend entirely on the state of your local repo. If there have been no changes since you last retrieved the code, you'll probably see just one line, something like the last one shown above. The details of the last commit [the last line above] will be different to that one above, which is a placeholder here in the docs. Don't expect that exact output; expect something similar to that.

2. Run the Cloudbox installer with your preferred tag (cloudbox, mediabox, or feederbox). Add any "non-default" roles onto the list of tags, separated by a comma.

   Examples:

   sudo ansible-playbook cloudbox.yml --tags cloudbox

   sudo ansible-playbook cloudbox.yml --tags cloudbox,emby,plexrequests

   Note: Install may quit if new changes were added into any of the .yml files (e.g. settings.yml) via the Settings Updater role. If this happens, check the the updated .yml file for the new additions and re-start the install.

3. Reboot when the install completes.

   sudo reboot