Until now I've used Tachyons in projects by using the CDN link. However on one occasion we were demoing with a client and Tachyons was not working. It was a bit embarrassing and at the time we weren't entirely sure why. It transpired that there was a temporary outage due to a version upgrade.
For github-backup, @SimonLab asked - should we download the Tachyons files to avoid this kind of event?
He said:
So I think it might be worth to create the Tachyons minimal file directly into the assets/css directory. We only need to remember to update this file manually if we want another version of Tachyons, we could maybe use npm to automatically fetch the last version of Tachyons and copy it on the assets directory but I don't think at this stage it's necesssary.
I recall this happening on BEP although it was a one off. As the stackoverflow article suggests - we could use the CDN and just specify a given version of Tachyons and that way it won't break.
Alternatively we could use the CDN and resort it to the saved files in the event that it's down as the SO article also says. Although I think that would be an enhancement.
I've created this issue to take note of this occurring and for discussion of best practices.
See: https://github.com/dwyl/github-backup/issues/22#issuecomment-367295826
Until now I've used Tachyons in projects by using the CDN link. However on one occasion we were demoing with a client and Tachyons was not working. It was a bit embarrassing and at the time we weren't entirely sure why. It transpired that there was a temporary outage due to a version upgrade.
For github-backup, @SimonLab asked - should we download the Tachyons files to avoid this kind of event?
He said:
CDN vs downloaded file: https://stackoverflow.com/questions/26192897/should-i-use-bootstrap-from-cdn-or-make-a-copy-on-my-server https://stackoverflow.com/questions/2145277/what-are-the-advantages-and-disadvantages-of-using-a-content-delivery-network-c
My thoughts were:
I've created this issue to take note of this occurring and for discussion of best practices.