fix path re-mapping here & in imars_puppet

[7yl4r]

The docker container the ERDDAP server lives inside is configured by imars_puppet. The paths used in this configuration are leftover from me testing things out and should be changed to pass-through the hypervisor unchanged.

For example, /srv/imars-objects/gom/chlor_a_l3_pass on the hypervisor is mapped to /chlor_a_l3_pass in the docker container.
It would be less confusing to just make it /srv/imars-objects/gom/chlor_a_l3_pass inside the docker container also.

This will require modifying a few lines here & a few in imars_puppet, then testing out the updated configuration.

[sebastiandig]

If I understand correctly, all I would need to do is change the volumes in imars_puppet to match the full file pathway and proceed to update the <fileDir> in the datasets to match the extended version?

ex. current:
volumes : /srv/imars-objects/modis_aqua_fgbnms/MEAN_7D_AQUA/OC:/fgbnms_modis_aqua_oc_7d
fileDir: <fileDir>/fgbnms_modis_aqua_oc_7d/</fileDir>

updated
volumes: /srv/imars-objects/modis_aqua_fgbnms/MEAN_7D_AQUA/OC:/srv/imars-objects/modis_aqua_fgbnms/MEAN_7D_AQUA/OC
fileDir: <fileDir>/srv/imars-objects/modis_aqua_fgbnms/MEAN_7D_AQUA/OC</fileDir>

[7yl4r]

Yes I think you get it. 👍

[7yl4r]

Everything should be ready in puppet now.
Among the potential complications I mentioned earlier, https://github.com/USF-IMARS/server-status/issues/24 was messing this up and has been fixed (for now).