-
Notifications
You must be signed in to change notification settings - Fork 746
Caching on the server? #793
Comments
[image: 内嵌图片 1] when use 2016-01-14 1:14 GMT+08:00 Glen [email protected]:
|
Great! I have some feedback/questions, if that's okay?
Sorry about all the questions! 😟 Thanks. =) |
But there is a risk, official npm seem not hope a 3rd source to sync from You are welcome! 2016-01-14 17:29 GMT+08:00 Glen [email protected]:
|
Your help is greatly appreciated, and there is no need to apologize. =) |
2016-01-14 20:44 GMT+08:00 Glen [email protected]:
|
|
This happened again with a clean installation, before installing any packages. |
perhaps some pkg your installed depend on 2016-01-29 20:44 GMT+08:00 Glen [email protected]:
|
I said that I didn't install any packages. I installed CNPM, started the server, and then it started to sync this |
where is the image [image: 内嵌图片 1]? |
Is it possible to set up caching on the server, so that requests for public packages are stored after being retrieved from the "source" registry?
For example, given the following "network diagram":
If client 1 requests a public package, is it possible to have that package stored on the CNPM server so that when client 2 installs the same package, it is loaded from there instead of being loaded from the source?
This should make the installation process a lot faster when the client has no cache of its own (f.e. a new Docker container).
Thanks. =)
The text was updated successfully, but these errors were encountered: