Dropbox sounds like a great idea, except for if it starts syncing an sqlite db constantly.
Another good option would be if we can make an nginx config (or a camping app!) which does WebDAV - finder, explorer, and nautilus all support it, and it means site upload bits and site serving bits both come from one program on the server, simplifying setup. — Jenna Fox On Saturday, 31 March 2012 at 5:28 AM, Dave Everitt wrote: > Having just spent a whole afternoon: updating my sources in Debian > just to install curl just to install rvm and check rvm requirements... > [paused here and logged out of server] to find that I now have to add > my user to the rvm group (to find useradd -G rvm myusername > *fails*)... then install a pile of Ruby dependencies that aptitude > can't even find... I'm all for this! > > I'd argue PHP became a default for web designers-turned-developers > partly because of the no-brainer beginner installation (dump all the > php files in your root dir!). > > So much is taken for granted and glossed over in both the Ruby and > Python communities about server setups, and there's so much outdated > and conflicting information out there, that a quick route (a la Heroku > but more selective and even easier) would be welcome. > > For a real no-brainer I'm even thinking Dropbox (which can run per- > user on a server) and/or git and/or a script that deploys once the > user is set both up on the server and locally, like cap deploy but > really stripped down. > > DaveE > > > On 30 Mar 2012, at 17:09, david costa wrote: > > > > I agree with Dave that we have to go pretty much back to basic when > > is about deployment. I have been running a free hosting for several > > years (2001 to 2006 I think http://dotgeek.org) and I think that > > many programmers get lost in running thins in reverse proxy which, > > as far as I gather, is getting the main web server (Nginx) to act as > > a proxy to your app more at > > http://blog.sosedoff.com/2009/07/04/how-to-deploy-sinatra-merb-applications-with-nginx/ > > > > From years in PHP this is already a big change :) Wondering if we > > could set up a free hosting for camping that is dead easy like on > > command line camping-remote myapp and make it run on the fly without > > having to configure anything and/or something where you simply drop > > your nuts.rb in the folder you want in apache/anything and it runs > > automagically or in a very simple way. > > > > But I am also very happy with how it works now :) just thinking loud! > > David > > > > > > > On Fri, Mar 30, 2012 at 4:59 PM, Dave Everitt > > > <[email protected]> wrote: > > > > I'll go with unicorn then. Apparently it handles more requests/sec > > > > than Thin. But that might be old benchmarks who knows. > > > > > > > > > > > > > > > > > Sounds great - my sites are the same setup, but with regular > > > > thin. :) > > > > > > > > > > > > > All I ask is that it avoids sentences such as this one (from > > > Unicorn): > > > > > > "Slow clients should only be served by placing a reverse proxy > > > capable of fully buffering both the the request and response in > > > between Unicorn and slow clients." > > > > > > Embarrassing to admit it and I'm going to look like a dumbo here, > > > but I don't really know what a reverse proxy is. I hate messing > > > with my servers (ancient Ubuntu and not-so-ancient Debian, running > > > Apache) any more than absolutely necessary. So I wouldn't > > > understand how to apply the information in that sentence, or - more > > > crucially - whether I can ignore it for a site(s) with small-to- > > > modest traffic. > > > > > > The Thin site does a nice, minimal job of explaining how to get > > > things running, but I'll be the first in line to watch the > > > deployment screencast and get Unicorn installed. > > > > > > After trying to teach this stuff to complete beginners and failing, > > > what I'm saying is: don't take any server-related knowledge for > > > granted when explaining deployment - this is where a lot of > > > frameworks fall down - I spent *days* trying to get one server > > > configured just to run something simple (okay, that was Django and > > > mod_wsgi - sshhh - but the same kinds of hoops still need jumping > > > through). > > > > > > > > > > I guess the bigger difference would be hooking one of the Rack > > > > servers to Apache instead of Nginx. But I think Nginx is a better > > > > option since it's ment to serve static pages and Unicorn will be > > > > the one handling all the dynamic stuff. > > > > > > > > > > > > > > > > ...but please include an Apache-only setup for those of us who > > > haven't installed Nginx (and really should, but just... haven't) > > > and have very modest loads, and a stack of legacy sites to run. > > > > > > > > > > the "simple dumbest" build will launch the webserver with thin > > > > (camping --port 80) > > > > > > > > > > > > > > > > Nice'n'simple, but (if starting out and watching a screencast) I'd > > > want to a mention of what dependencies need installing on my server > > > to even get that far... I'm carrying on as dumb here because even > > > getting SQLite running on my old Ubuntu server (for a default > > > Camping setup) took some fiddling. SO maybe a quick: "here's how to > > > check you have SQLite running on your web server: `which sqlite3` > > > or `sqlite3` then from the sqlite shell `.quit`". > > > > > > DaveE > > > > > > > > > this is what Unicorn sounds like: http://d.pr/olau > > > > > > LOL! Now I know. These little asides are what keep me in this > > > community, and _why I came here in the first place. > > > > > > > > > _______________________________________________ > Camping-list mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/camping-list > >
_______________________________________________ Camping-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/camping-list
