I've been testing with switchpipe for some time now, and I really like
it.
Before making a 'permanent' move to it on our production servers, I
would like to know about support/maintenance plans for the future.
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?
Of course I know that - as switchpipe is an open source project - I
don't have any guaranties.
I don't need that either, but some intentions the author has with this
project will give at least some indication if this is worth the move.
I read about the future/todo plans, so I know there is more coming in
the future.
But how about after that? Any intentions to keep and maintain this
project? Or will the 'proof of concept' be finished when all features
are in?
Anyway, big thanks for switchpipe as it is right now.
We have many 'small' customers that don't have busy sites, mostly
peaks at certain times.
Right now everything together takes up a huge amount of memory, so
switchpipe is perfect for the job.
> 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.
