Sorry, perhaps I should have explained in a little more detail in my original email. Basically users can create templates in the system using docx documents. These templates can be populated defined place holders and when they generate a document in some content from the system the place holder values will get replaced with actual values. The generated document is automatically stored within a documents repository in their account. Users may want to edit these generated documents to make small amendments to them. Currently they have to download the document to their local machine, make the changes and upload it back again which results in them having two versions of the same document (unless the delete the previous version). To make this easier for users I wanted to see if there was some mechanism so when they open the document for editing on their local machine that this could be saved directly back to the server overwriting the original document. I don't want to insist that users have a subscription to Office 365 etc in order to use this feature in the system as many have a version of MS Office or OpenOffice already installed locally on their machine. On 23 January 2015 at 14:30, Stuart Dallas <stuart@xxxxxxxx> wrote: > On Friday, Jan 23, 2015 at 12:59 pm, Adrian Walls <awalls@xxxxxxxxxxxx>, > wrote: > >> I'm trying to find a solution which via our application would open a >> document (docx) stored on AWS S3 allowing a user to make amendments to the >> document on their local machine via MS Office or OpenOffice but when they >> click save it would automatically save the document all the way back to >> S3. >> >> Is this something that would be possible to implement and if so I'd >> appreciate any suggestions as how I would go about it. I've had a look at >> Webdav but I'm don't think it's suitable for this task as the documents >> are >> stored in various different accounts on the system plus I can't see how to >> push this all the way back to S3. >> > > You're basically asking for an implementation of DropBox, and there's no > way I'd choose PHP to implement something like that. There are apps that > can mount an S3 bucket as a local drive, but again that's not something > you'd do with PHP. > > To get PHP involved (tho I don't see why you would) you'd need the user to > take the extra step of uploading the edited document when they're done. > > However, why not just have them use Office365? > > -Stuart > > -- > Stuart Dallas > 3ft9 Ltd > http://3ft9.com/ > -- Adrian Walls 23sparks Tel: +44 (0) 28 4179 8226 Mob: +44 (0) 77 3447 3615 Email: awalls@xxxxxxxxxxxx Web: http://www.23sparks.com Registered office: 8 Osborne Promenade, Warrenpoint, Newry, Co. Down BT34 3NQ Registered in Northern Ireland no. NI50666 CONFIDENTIALITY NOTICE This email is private and confidential and may contain legally privileged information. If you are not named as an addressee it may be unlawful for you to read, copy, distribute, disclose or otherwise use the information contained in this email. If you are not the intended recipient of this email please destroy this communication and contact awalls@ <awalls@xxxxxxxxxxxx>23sparks.com.
