You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
- 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
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.
The text was updated successfully, but these errors were encountered: