How to upload file to the dynamic subdirectory?

[bocharsky-bw]

How can I create a custom namer which could generate some hash like d74a1cb2f57966565d735c6332b77474.jpg and then split it to the few subdirectories like /d7/4a/1cb2f57966565d735c6332b77474.jpg, so the resulting file 1cb2f57966565d735c6332b77474.jpg uploads to the '%upload_destination%/d7/4a/' directory.

Can I do it with VichUploadBundle?

[bocharsky-bw]

I think the main problem I faced with this issue is that directory namers MUST be stateless.

Could you explain us some benefits why there should be subfolders used? I saw similar in the Twig cache storage but as I understood it only results in better performance if you use 1000 or 10000 files in a folder, right?

It would be nice to understand this more - maybe there are some benchmarks about that.

[bocharsky-bw]

👍 @JHGitty I don't have any performance benchmarks personally, but you're right! I consider it with a performance point. And yes, I try to implement something what Twig do for all my uploads.

I found that there is already a "directory namer" interface: https://github.com/dustin10/VichUploaderBundle/blob/master/Resources/doc/directory_namer/howto/create_a_custom_directory_namer.md

I think the directory namer is made for your requirements, isn't it?

[bocharsky-bw]

@JHGitty I think, the main problem is that:

directory namers MUST be stateless

See notes in namers.md. I tried to use my custom directory namer to resolve this but I failed. Seems directory namer is independent of file namer. Maybe one of the possible solutions is to make directory and file namers aware about each other.

@K-Phoen I think this issue should get the Enhancement label.

[K-Phoen]

I think that what @bocharsky-bw wants to do is already feasible. The directory namers are called after the file namers and have access to both the object and the mapping.

So using the filename to generate a directory name should already work :)

[bocharsky-bw]

@K-Phoen Yeah, looks like it works already but with some bugs on update/remove. I guess it happens because file namer only calls for uploading files, but directory namer also calls for updating and deleting. Actually, directory namer is called even to display already uploaded image, always. I think this is a strange usage of directory namer.

As a file namer, directory namer should be triggered only on uploading, I think.

[Koc]

@bocharsky-bw see related PR