Re:The sad state of sysadmin in the age of containers (2015)
by weberc2 on Monday December 09, 2019 @07:50AM
(#21742142)
There’s a pretty straightforward solution to this problem which is to run your own NPM server even if it’s only a caching proxy. For some orgs, the uptime provided by the third party servers is sufficient.
[ Parent
| on HN ]
Re:The sad state of sysadmin in the age of containers (2015)
by doomslice on Monday December 09, 2019 @09:04AM
(#21742686)
Having been at 3 companies that did this, I can say with certainty that our caching proxies (artifactory in all of them) were much more likely to go down than the public repos were.
Re:The sad state of sysadmin in the age of containers (2015)
by _-o-_ on Monday December 09, 2019 @10:48AM
(#21743591)
Yeah, I think I've lost a day in total when our local npm was finicky on several occasions or failed to fetch latest version of a package that we've developed in house, but made publicly available.
Re:The sad state of sysadmin in the age of containers (2015)
by llampx on Monday December 09, 2019 @12:16PM
(#21744333)
They just don't have to be down at the same time to be useful.
Re:The sad state of sysadmin in the age of containers (2015)
by regularfry on Monday December 09, 2019 @09:51AM
(#21743092)
Yes, but at least in that case you have the fallback of the public repos.
Re:The sad state of sysadmin in the age of containers (2015)
by CathedralBorrow on Monday December 09, 2019 @09:21AM
(#21742837)
Maybe it's obvious and straightforward enough that other people have come up with the same idea, tried it and not found it to be worth the effort?