User supplied File ID (enhancement)

[GoogleCodeExporter]

Users can skip the assign step and simply post to the weed-fs cluster with a 
POST containing their own unique ID.

example:

> curl -F file=@/home/chris/myphoto.jpg http://127.0.0.1:8080/myphoto.jpg

Can later be retrieved

> http://localhost:8080/myphoto.jpg

Or deleted

> curl -X DELETE http://127.0.0.1:8080/myphoto.jpg

This would eliminate double calls and function more like a volume.  Static 
assets, for example, could be called as easily as <img 
src="http://weedfs-cluster.com:8080/myphoto_thumb.jpg">

Original issue reported on code.google.com by kevinste...@gmail.com on 27 Nov 2013 at 12:14

[GoogleCodeExporter]

This can be achieved with a simple server in front of weed fs. The server will 
use a key-value store to map url to the file id, and fetch the file id from 
weed-fs, and pass the content out.

Original comment by chris...@gmail.com on 27 Nov 2013 at 12:57

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

The simple server in front of weed-fs requires me to cluster that as well if I 
want to provide scale-out without a single point of failure.  I want to use 
weed as the key value store! :)

Original comment by kevinste...@gmail.com on 27 Nov 2013 at 2:27

[GoogleCodeExporter]

In our proof-of-concept setup, we use Redis as the (persistant) key-value 
store; works like a charm

Original comment by ernest.m...@gmail.com on 25 Jan 2014 at 9:10

[GoogleCodeExporter]

Hi, Ernest, it will be great if you can share your code to do this. Or maybe 
create an open source project for it.

Original comment by chris...@gmail.com on 25 Jan 2014 at 8:10

[GoogleCodeExporter]

A "weed filer" option is added.

Original comment by chris...@gmail.com on 10 Apr 2014 at 8:45

• Changed state: Fixed