separate settings for source and target directory

[ghost]

Source images does not have to be accessible from web root. There are some use cases when it is not desirable.

E.g. we could have HQ photos and only show medium-sized, watermarked photos.

[LouTerrailloune]

You can implement this with a custom DataLoader.
I did this, and add a prefix to my images path. The loader translate the prefix from the image path to an absolute path.

Adding a global source path might be interesting, but in my case I have many source paths, and this will require a parameter in the twig filter.

[ghost]

You can implement this with a custom DataLoader.

Of course, but what I think is the correct way is the configuration option.

 I did this, and add a prefix to my images path. The loader translate the prefix from the image path to an absolute path.

 Adding a global source path might be interesting, but in my case I have many source paths, and this will require a parameter in the twig filter.

Keep in mind that in your example you can also use symbolic links within one, dedicated source directory.

[lsmith77]

i have just made custom data loaders a lot more flexible by allowing per filter set data loaders. the main reason for this is to prevent users from having to create data loaders that can handle multiple data sources.

at any rate if you need to do this, i would suggest you simply redefine the file system loader with a different root path. note i also just renamed the "webRoot" property to "rootPath" in the file system loader to make clear we just care to get a base path.

[lsmith77]

just to further explain this: i don't want to add data loader specific configuration options in order to keep things more focused. creating a custom service isn't so hard and its config only as the code is ready to handle your use case.

[ghost]

Sure. No problem :)