MiningOps Get a license

Guides

Updates and database copies

Your license includes every release published during its year of updates. Your site installs them itself, and keeps copies of its databases on your server.

You'll need

  • Your MiningOps site, signed in as an admin.
  • For copies kept elsewhere: SSH access to the server.
  1. Update the site

    Open Settings → Updates. A dot on the tab means a new release is waiting. Select Check now to look straight away, then Install.

    The site makes a copy of its databases first, then installs the release and restarts. The rigs keep mining throughout. Each release's notes are on the releases page.

  2. Update the rigs' agents

    When a release brings a new agent, each rig's page shows Update agent in its Miner panel. Your site signs every agent update with its own key, and each rig checks that signature before it installs anything.

  3. Know where the copies are

    The site copies its databases every night and before every update, into:

    sudo ls /opt/miningops/miningops-private/backups

    It keeps the newest five copies, the newest of each of the last seven days, and the newest of each of the last four weeks.

  4. Keep a copy somewhere else

    Copies on the same server don't help if the server's disk fails. Copy them to another machine now and then, for example:

    sudo rsync -a /opt/miningops/miningops-private/backups/ you@backup-host:miningops-backups/

When your year of updates ends

Your site keeps running on the version it has, and keeps working as before. Renewing adds another year of updates under the same key. Your license page shows when your updates end.