-
Notifications
You must be signed in to change notification settings - Fork 0
Configure XNAT Post Install
As of XNAT 1.9, the container service sets the Image Hosts registry as https..dockerhub. This will fail with Swarm mode enabled, and 'https://' must be removed. Edit the settings. If using a private registry, omit the https://.
- Click on Plugin Settings under Administer.
- Click on Edit for the registry: Compute Backend -> Image Hosts -> Edit
- remove https:// - https:// hub.docker.com -> hub.docker.com
- Log on as user: admin, pwd: admin.
- Click on Users under Administer.
- Click on the xnat_admin user defined in xnat.cfg. Make sure the user is Verified and Enabled. Click on Change Password to set a new password.
- Click Save
- Log off the default Admin user. Log on using the new admin account. Go back to the Users page.
- Click on user Admin.
- Deselect Enabled.
- Repeat for Guest.

The archive, database and log files are localted int eh /xnat-data directory as explained the XNAT Setup Overview
To change the location, for example locating the archive data on external storage, read Maintenance and Scripts
You can backup all the containers and storage using the script:
cd Linux sudo ./save_and_restore.sh save
This will create a directory backup. Back this up.
All the storage is located by default under /xnat-data.
The archive is located in:
/xnat-data/xnat/archive
The postgresql database is located in:
/xnat-data/postgresql
A nightly dump of the database is made:
/xnat-data/xnat/scripts/pg_dump
These should be regularly backed up. For example, if you ahve network storage, you could sync this folder nightly and add as a nightly job. This example syncs pg_dump at 2am every night:
sudo crontab -l > mycronjobs
echo "00 02 * * * rsync -avu --delete /xnat-data/xnat/scripts/pg_dump [path to network location]" >> mycronjobs
sudo crontab -u root mycronjobs
https://gitlab.com/KCL-BMEIS/Data-Analytics/DaDa/-/wikis/DQR-Pluigin-and-Testing