Open metasoarous opened 13 years ago
I'm not interested in Heroku so thats why I've not looked at this issue before, but this looks like a good start on modularising rubycas-server.
I would really like to see ruby's-server broken into two projects. A rack gem and a sample sinatra application that utilises the gem. I think this would be a better separation of concerns and make it more flexible whilst reducing responsibility of the core system.
If there is support for this I will gladly help out.
It's surprising to me that there has been less Heroku interest than there has, given how popular Heroku is as a hosting service. In any case,...
The project I was working on that required a CAS was cancelled, so I haven't had much of a personal need to continue progress on this fork. However, I would be happy to help in my spare time, particularly if my fork is used as a basis for modularization.
Regardless of whether or not there has been an outcry of interest in Heroku and other read only filesystem support, it definitely seems like a good idea that will only make the project stronger. And obviously modularization in general is a good idea.
Chris
Any progress on this during the past two years? I'm in the middle of migrating our apps to Heroku and we need RubyCAS to work there.
I did some work in order to get this working on heroku. It would be great to have this merged in with the main branch.
https://github.com/metasoarous/read_only_rubycas_server
Cheers
Chris Small