Make the local copy of CDN hosted files optional

[Kris-LIBIS]

Refering to #98, I agree that copying the JS and CSS files locally seems like a good idea. Practically, however I have some concerns.

The files are hosted on CDNs which are typically beefed up servers spread geographically and have features like ETAGs and automatic upscaling that make them very much optimised for the task. By copying the files locally we not only expose ourselves to side effects like the one mentioned in the issue above, but we direct more traffic to our local server that is often not optimised for dealing with spikes.

I assume that the local copy is intended for speeding up the loading time, but it may have an average effect. When I am moving all the CDN files to my local server in Belgium, a researcher in Argentina would need to fetch all the files from our server in Belgium. Loading them from a CDN host - even if the closest one would be in Brasil - would be way faster.

Here is an excellent article discussing why using a CDN is often a better option than hosting locally. Most browsers currently implement cache partitioning, so the cross-domain performance gain is no longer a given, but the other advantages are still a thing.

I would therefore suggest to make executing the localinstall.sh from the init.sh optional and even an opt-in (default no local install). The readme should also make users aware of the consequences of copying the files locally.

[qqmyers]

@Kris-LIBIS - just checking - is there something in the PR#98 in this repo that's a problem? (init.sh is not in this repo). If you'd like to suggest changes to the readme, please do.

[Kris-LIBIS]

@qqmyers My bad. I was referring to the init.sh in the dockerized version, but wrongly assumed it was also part of this repo. The suggestion to the readme might still stand, not?