Mike Virata-Stone

Yeah, I meant we should log any error we detect (the problem I had was I kept looking at the log and not seeing any error, yet my gemstash server...

Maybe something like `gemstash preload`? or maybe even a way to preload specific gems? like `gemstash preload rails`? How should all versus latest work? Maybe `gemstash preload --latest`? What if...

@indirect keep in mind certain requests will still be directed towards rubygems.org, such as dependencies... those cache for 30 minutes and then will get re-fetched from rubygems.org after that... and...

Would "backend gone" mode require --full-index, or are we going to try to serve dependencies from the locally cached gems? Also, I have an idea for prefetching specific gems.... we...

Is this purely limited by bandwidth and IO, or would it maybe get a speed boost by going multi-process? Would this mode be putting stuff in the database and behaving...

:+1: I think 3 level or 2 level depth would be fine, maybe 3 level just for the added protection, or is that unnecessary? If we do 3 level depth...

Fair enough, we could use it as is; however to me, pushing that on the user of the storage class means that every user of the class now has to...

I did a #26 to try it out... seems like pretty minimal footprint to make the Storage class protect against it in the general case... feel free to share thoughts...

`-` doesn't seem to be a real problem, at least on my linux laptop... I created the directory fine (though trying to change into it seems a bit harder)