Closed techgique closed 7 years ago
@techgique FQDN? (sorry a bit slow today)
I think this is mostly figured out. Image and audio configs are in the config file, so we can put things wherever, we just need to decide and mark in the config. Leaving this open till we decide exactly where to store things.
Rename /var/local/www/figures/
to /var/local/www/media/
,
updating Everyweek and OSCYS projects relying on it.
Add L&C audio and images to:
/var/local/www/media/lewisandclark/audio/
/var/local/www/media/lewisandclark/images/
OK another part to this issue, we need to decide where to link to the xml for the site.
A couple of other site examples:
thinking this through, once we have the API, the XML will always be stored in one central location so it is accessible from the API. so really, it shouldn't come from the root URL
Collecting ideas for a data repo URL:
cdrhmedia.unl.edu CNAME in place. Request for TLS cert in, but not processed yet. Browse site and make sure images are serving properly through HTTPS and no mixed-content problems after set up.
DOOOONEEEEE
Image URLs are hardcoded with live site's FQDN. Karin has images stored in data_images on Rosie
Do we want to move them to cors1601 and remove FQDN from links?