Difference between revisions of "Updating CryoSPARC"

From UFRC
Jump to navigation Jump to search
(Created page with "If you have a CryoSPARC instance running in PUBAPPS a representative from a group who requested access to the instance can update CryoSPARC when an update becomes availabl...")
(No difference)

Revision as of 18:04, 10 May 2024

If you have a CryoSPARC instance running in PUBAPPS a representative from a group who requested access to the instance can update CryoSPARC when an update becomes available in the interface.

Note: use the correct group name instead of 'GROUP' below.

  • Log into the webserver from HiPerGator
$ ssh cryosparc

Note: the above 'cryosparc' profile is configured for the group representative user(s).

  • Run a manual database backup in addition to the nightly automated cryosparc database backups:
$ cryosparcm backup --dir=/blue/GROUP/apps/cryosparc/db_backups
  • Change into the cryosparc_master directory
$ cd /privapps/GROUP/cryosparc/prod/cryosparc_master/
  • Stop the cryosparc instance
$ systemctl --user stop cryosparc
  • Update the master

$ cryosparcm update

  • Copy the worker update bundle

$ cp cryosparc_worker.tar.gz cryosparc_worker/

  • Update the worker

$ cryosparc_worker/bin/cryosparcw update

  • Restart cryosparc

$systemctl --user start cryosparc

Please let us know if you need help via [1]