Is the an option not to cache third-party files

[jalateras]

I'm looking at always serving third-party modules from https://registry.npmjs.org and only store and serve private modules from sinopia. Does such an option exist?

[rushes]

yeah this would be very useful to us too

[rlidwka]

How is it different from what it does now? Are you worrying about a disk space, or is it something else?

[jalateras]

@rlidwka main issue for me would be around disk space.

[rlidwka]

@jalateras , for now you can separate private modules from third-party ones, and move cache to /tmp/ for example (which you can remove at any time):

packages:
  'private-*':
    allow_access: user
    allow_publish: user
    storage: /tmp/

  '*':
    allow_access: all
    allow_publish: user
    proxy: npmjs
    storage: local_storage

I'll try to add support for not storing them at all, should be easy enough.

[jalateras]

great. I'll give this a go.

[rlidwka]

I added an option in sinopia@0.9.1, now you can specify storage: false in config file, and specified packages won't be stored to the disk.

But I'd suggest not to use it unless you have to, because it will consume a lot more traffic:

• There will be no HTTP 304's for them, all data will be transmitted even if npm downloaded it previously. That's because normally ETags are stored to the hard disk.
• For each tarball you request, sinopia will make two requests to the upstream (first to get package info, and second to get tarball itself). Normally it'll be just one request because package info is retrieved from hard disk.

But I suppose if you care about hard disk space more than about performance and bandwidth (embedded systems? mini-server like raspberry pi?) this would be useful.

[jalateras]

@rlidwka Great!! I'll upgrade to 0.9.1 and give it a go,