Skip to content
This repository has been archived by the owner on May 4, 2023. It is now read-only.

Use a remote File Storage system #12

Open
Potherca opened this issue Feb 17, 2014 · 1 comment
Open

Use a remote File Storage system #12

Potherca opened this issue Feb 17, 2014 · 1 comment

Comments

@Potherca
Copy link
Owner

To be able to run this on Heroku we need to move file storage away from the local file system and into some external file storage. The Amazon Web Services Simple Storage Service (AWS S3) seems a good candidate, although other candidates are also available (RackSpace, Google Cloud, etc. Or we could abuse Dropbox/Copy.com style services).

The easiest way to implement this would be to refactor the code to use the FlySystem local adapter and when this works, switch over to the AWS S3 adapter. This would also make development easier as we could make the adapter configurable. (We wouldn't want to use up our entire free quota just debugging, now would we?)

If an other service provider seems more attractive than AWS we could create an adapter for it.

@Potherca
Copy link
Owner Author

Potherca commented Aug 1, 2014

Eventually it might be nice to allow end-users the means of saving stuff to a service of their choice.
This needs to be taken into account when implementing this.

@Potherca Potherca added ready and removed ready labels Aug 1, 2014
Potherca added a commit that referenced this issue Aug 26, 2014
 - Reads available output types from graphviz  output (see issue #14)
 - Hooks FlySystem into the code (using the local adapter for now, see issue #12)
 - Uses stream wrapper for input/output when running the shell commands
@Potherca Potherca added the ready label May 2, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant