The main problem is the ridiculous amount of things based on s3. Mainly S3, S3File, and S3Request.
The main way to do this would be this:
1. Make a class that had functions like getFile, getRequest, etc. I don't know what you'd use for S3. I've written down every use of the functions on each of the S3 classes, and I'm working on extracting an interface.
2. After you create the interface for the files, have it figure out which one to use based on a configuration file define or dependency injection.
3. Modify the passthru function to read the local file instead of the remote file.
4. Make things like the job upload function which links directly to S3 upload somewhere else.
5. Make sure all Urls are now correct and don't point to S3.
Basically, that's about it. I'm working on refactoring BotQueue to make it more testable so I'm not going to just slap a solution on there to say it's done.
I will say, however, that it is currently in progress.
Justin Nesselrotte
--
You received this message because you are subscribed to the Google Groups "BotQueue" group.
To unsubscribe from this group and stop receiving emails from it, send an email to botqueue+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Justin,
Has there been any progress on this feature? Is there a local storage (non S3) solution available? Is there something I can do to help?
Manuel Beltran
You received this message because you are subscribed to a topic in the Google Groups "BotQueue" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/botqueue/ibRSMPKoccM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to botqueue+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.