> Since rails server/proxy solutions seem to come and go these days, I
> don't want to rush anything new.
> Since switchpipe is announced as a "proof of concept", how can I feel
> about the intentions with this project?
SwitchPipe is very much a "gap filler" driven by immediate need. I
very much hope someone will come along with something that removes the
need for SwitchPipe entirely, but currently nothing exists that does
the same things as SwitchPipe and makes it as easy. There's a
"mod_rails" in the pipeline, due to arrive soon, but that's still
focused just on Rails, so I don't see any replacements soon.. so
SwitchPipe will continue to live :)
I use SwitchPipe for my own Ruby related Web app deployments, and as
long as I'm using it, it'll be updated in some form or another. There
is no large team behind SwitchPipe, however, and unless it's minor,
I'm probably not going to be adding significant numbers of features
that I, personally, wouldn't use.
SwitchPipe is highly unlikely to evolve into something significantly
bigger than it currently is. I want to keep it small, agile, and
suited for its primary tasks.
> Will EBB be considered as backend option?
If you can run an app backed by Ebb from the command line, effectively
you can already do it with SwitchPipe. It's not a "named" option at
present though, no, but could quite easily be added to the hash.
Cheers,
Peter Cooper