`siteUrl` currently exists in two places

[paddyroddy]

Short Description

Currently, siteUrl exists in two places:

1. ansible-collection-infra/roles/xnat/templates/prefs-init.j2

   Line 4 in 163a8dd

   siteUrl={{ xnat_web_server.url }}

2. ansible-collection-infra/roles/xnat/templates/xnat-settings.json.j2

   Line 74 in 163a8dd

   "siteUrl": "{{ xnat_web_server.url }}",

It seems that only the latter is actually used. Possibly the latter overwrites the former? Either way, this should be addressed.

Evidence/Steps to Reproduce

No response

Acceptance Criteria/Expected Behaviour

No response

Details

No response

Resolution

No response

[p-j-smith]

Looking again at this, all of the variables in the siteConfig section of prefs-init.j2 are repeated in xnat-settings.json.j2.

ansible-collection-infra/roles/xnat/templates/prefs-init.j2

Lines 1 to 18 in 163a8dd

	[siteConfig]
	siteId={{ xnat_config.site_name }}
	siteUrl={{ xnat_web_server.url }}
	adminEmail={{ xnat_common_config.admin_email }}
	archivePath={{ xnat_archive_dir }}
	prearchivePath={{ xnat_prearchive_dir }}
	cachePath={{ xnat_cache_dir }}
	buildPath={{ xnat_build_dir }}
	ftpPath={{ xnat_ftp_dir }}
	pipelinePath={{ xnat_pipeline_dir }}
	requireLogin=true
	userRegistration=false
	enableCsrfToken=true
	sessionTimeout=1 hour
	initialized=false

The only difference is the value of initialized, which is true in `xnat-settings.json.j2. I think we probably don't need to set them again with the config (or alternatively remove them from the prefs-init).

And the XNAT docs suggest that you only set the paths (archivePath etc.) once, and then don't change them. Not sure what would happen if we changed these paths during an upgrade?