Is it possible to store published packages & cached packages in different directories / with different storage plugins?

[lluiscab]

Currently, private packages published to verdaccio and public npm packages cached by verdaccio are all stored on the same directory, with no way (other than reading the database file) of knowing whatever a package is a cached or published and therefore making clearing the cache after some time rather difficult.

Is there any way to configure Verdaccio such that it'd use different storage directories (or even plugins!) for cached and published packages? Ideally I'd like to use the local filesystem for cache and a S3 compatible object server (MinIO) for published packages.

My current configuration looks like this:

(...)
storage: /verdaccio/storage

uplinks:
  npmjs:
    url: https://registry.npmjs.org/
    maxage: 12h
  yarn:
    url: https://registry.yarnpkg.com/
    maxage: 12h
(...)

[lluiscab]

sorry to ping you directly @juanpicado, but could you take a sec and look into this? I'd like to know if what I'm requesting is an already existing feature or if it'd have to be implemented (and if I may be able to do so).

[juanpicado]

sorry to ping you directly

No issue as long nobody abuse of it.

Is there any way to configure Verdaccio such that it'd use different storage directories (or even plugins!) for cached and published packages? Ideally I'd like to use the local filesystem for cache and a S3 compatible object server (MinIO) for published packages.

Currently no, for context, the original project design allowed multiple authentication plugins, then the filters plugins was added later on but storage always was assumed there is only one.

It's not impossible to make it but is a very big effort to achieve it. It has been on my mind few times but since the bigger audience does not need it and is very specific I always discarded the idea and focus in other topics.

If you ask me I'm not working in that direction at this moment, maybe in the future but not this year.