Skip to content

Conversation

@nemo
Copy link

@nemo nemo commented Jul 10, 2013

Added support for saving onto S3 instead of disk. Had to add an abstraction layer between the two file stores, nothing special. I thought it'll be a good addition.

This is primarily because we're thinking about running Batsd on heroku / production.

@noahhl
Copy link
Owner

noahhl commented Jul 15, 2013

Wow, thanks! This is a great idea.

I'm going to hold off on merging it until I merge in the dev branch, which uses a more efficient file structure (and the benefits of it will be doubly felt on a datastore like S3). That's almost ready to go, just needs new documentation and migration instructions.

@nemo
Copy link
Author

nemo commented Jul 15, 2013

Okay, cool :)

I suppose I'll have to move some things around after your merge, since you're using a new system? Or will you be taking care of that :)

Either way works!

On Jul 15, 2013, at 8:27 AM, Noah Lorang notifications@github.com wrote:

Wow, thanks! This is a great idea.

I'm going to hold off on merging it until I merge in the dev branch, which uses a more efficient file structure (and the benefits of it will be doubly felt on a datastore like S3). That's almost ready to go, just needs new documentation and migration instructions.


Reply to this email directly or view it on GitHub.

@bastiaanterhorst
Copy link

Is there any progress on this? I'd love to use the S3 functionality.
Otherwise I'll go ahead and use @nemo 's fork (hoping that transitioning to the new data structure will be possible).

cheers,
Bastiaan

@mikekreeki
Copy link

Any updates on this? Being able to run batsd on Heroku would be a great feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants