5 replies to this topic

[vanderbreye]

Hej!

Has anyone ever tried to save & load the files in / from the S3 instead / beside of the local filesystem ?

by using http://framework.zen...zend.cloud.html it is very esay to implement to save/load:
http://blog.ebene7.c...pper-verwenden/
- but will PW work with it?

By module? Or even better: a plugin that automatically saves/serves any files handled by the backend..

We will now try to build this, but we'll also happy about any thoughts about it!

[Marty Walker]

Hi vanderbreye,

I'd love to see something like this is PW. I've used one or two add-ons for ExpressionEngine that do similar. Are you, by chance, planning any features that allow users to only have access to the files they've uploaded?

Regards
Marty

[Michael Murphy]

Hi vanderbreye,

I like the idea - I've always wanted the ability to use dropbox for site assets, as it would be a much smoother workflow especially when working with others (eg. use a shared folder and eliminate the need to use the web interface to update files).

@diogo mentioned this interesting service a while ago which might be worth investigating

https://www.filepicker.io/

not sure if it works both ways - I think it just gives you a simple interface to the files which would then be uploaded to your server

[diogo]

@diogio mentioned this interesting service a while ago which might be worth investigating

@diogo

[vanderbreye]

Ok, it is simple to implement the S3 directly in the core upload

BUT: how should i begin to write the module, which binds on the uploadprocess?
It is important to have file+tmp name of all uploded files in it. is there a hook i can use?

a) hook in the uploadprocess and
c) give a global option where to place the files: local / AWS / or both.
hook in the output of the images+thumbs (based on options location)
d) hook in the backend thumbnail view to show (based on options location)

[ryan]

Something that is storing images exclusively on another server probably needs to be a different animal from the existing image/file fieldtypes. Rather than trying to hook into functionality there, I would go and create a new fieldtype so you can start fresh. On the other hand, if the goal is to just keep a copy of any files used at the other server, and then replace references to them at runtime (like when output formatting is on or something) then I think that would be more of a scenario where hooks would be useful.