Closed zeke closed 11 years ago
Actually you dont need a RepositoryGroup if you arent aggregating multiple repositories. Looks like this is a simple s3 proxy so I think it should work as is?
On Mon, Jul 22, 2013 at 11:46 PM, Ryan Brainard notifications@github.comwrote:
Almost, you also need to create a RepositoryGrouphttps://github.com/heroku/s3pository/blob/21ac2cfbb42dceaf01020ab9a16e0fb1ade5a6dc/src/main/scala/com/heroku/s3pository/S3rver.scala#L87-L89and add it to the 'servicehttps://github.com/heroku/s3pository/blob/21ac2cfbb42dceaf01020ab9a16e0fb1ade5a6dc/src/main/scala/com/heroku/s3pository/S3rver.scala#L133. The /jvm group is called all because everything so far was JVM-only, but you should be able to create your own Node group in the service. +@sclasenhttps://github.com/sclasenin case I'm missing something.
— Reply to this email directly or view it on GitHubhttps://github.com/heroku/s3pository/pull/12#issuecomment-21396128 .
Almost, you also need to create a
RepositoryGroup
and add it to theservice
. The/jvm
group is calledall
because everything so far was JVM-only, but you should be able to create your own Node group in the service. +@sclasen in case I'm missing something.