Question about how to newly added resource

Hi, thank you for creating this wonderful project.

I’m using sirv with sapper to serve some static images. And these images can be uploaded through back-end. Then these images will be relocated to sirv’s dir.

Because sirv will only scan file-system once when it’s imported, these newly added images will not exists in cache, so you get 404 when visit these images in browser.

So my question is, can we add some logic, like lookup file-system when resource not found, to handle newly added resource?

[lukeed]

Hey, than you 😃

There’s no way to expose/update the cache post-startup. This is intentional. What I would recommend doing is organizing your assets in such a way that your assets (the website’s) are in one location, and the dynamic, user-uploaded images are somewhere else.

Then you would run two instances of sirv – a “dev” variant for the user images (since theyre transient) and “prod” for your own.

PS: You also would not want a never-ending supply of images being added to your internal cache. That would cause high memory usage very very quickly.

The final snippet would roughly look something like this:

sirv('public/static'); //~> cache instance on your own assets
sirv('public/uploads', { dev: true }); // -> fs reads on dynamic asset supply

Hope that helps!

[lukeed]

Thanks. Feel free to open an issue/RFC and it can collect feedback. Please include any relevant API/option suggestions for how it might be done, because at this point I can’t imagine a non-confusing way to distinguish between “just what’s here”, “use file system”, and “do both”.

It might be worth considering for a 2.0 at some point – at which time I’ll also be sure to rename the option.