Maintain Datasets Files between the different servers

[JessyBarrette]

ERDDAP is generally handling data from

• Database
• Files on the server (mounted within the container)

For the files we have as of now a copy on each server:

• catalogue.hakai.org
  • [x] /data/erddap_data : /datasets
  • [x] /mnt/efs/algex /algae_explorer
• goose.hakai.org:
  • [x] /data2/erddap_data : /datasets
  • [x] /mnt/efs/algex /algae_explorer

Typically we may not always want the development branch to present the same data as production so theres occasions where we would point an dataset to different files in production vs development.

So ideally it would be great to have the /data/erddap_data folder been a mounted volume on each server and potentially have a second development volume for just development purposes. This last one could be potentially on the actual server if we want.

[JessyBarrette]

Looking further into this, it seems like both ERDDAP data files on the respective servers are coming from an external mounted drive already:

goose:

/dev/nvme1n1                                              131919812  91457080         34742196  73% /data2
/dev/nvme4n1                                              514937088 245891732        242814572  51% /algae_explorer

catalogue

/dev/nvme1n1                                               65531436  48159560         14000052  78% /data
fs-0da5688cab7d32c08.efs.us-east-1.amazonaws.com:/ 9007199254739968 815926272 9007198438813696   1% /mnt/efs/algex

[JessyBarrette]

This issue is now resolved both files from goose and hecate were both copied to EFS mounts both mounted on the new erddap server