From: "T. W. Urp" <twu@...>
Date: 2007-02-26T09:55:07+09:00
Subject: Re: No Rails, shared host - what would you use for DB and Se

a On Sun, 25 Feb 2007 20:35:00 +0900, Chris Lowis wrote:
> If you're looking to write your own software to do this, you might find
> inspiration in the Camping micro-framework:
> http://camping.rubyforge.org/files/README.html
> 
> Camping uses ActiveRecord for its DB abstraction and also has a simple
> session management system :
> 
> http://code.whytheluckystiff.net/camping/wiki/CampingSessions
> 
> Best regards,
> 
> Chris

Thanks for the lead Chris and Giles, I immediately got Chris's advice, and
am digging through the ActiveRecord classes in the api. :) Evening read is
the Camping source...

I want everything to be as simple and small as possible, but with security
all over the place.

Despite reading the Camping files through, I still get the impression that
Camping requires its own mini-server, root access to server or Rails
(and/or ActiveRecord) running in the server memory.

This is not possible with many shared hosters, and in fact, to make code
as universal as possible (aim here), it has to be php/perl-cgi type of
app. Am I reading wrong into the Camping module description?

My motivation for this project is exactly this type of misguided
thinking that does *not* meet the needs of the larger web-community. 
 
Some of the typical questions that constantly pop up before me, in form
of Ruby APIs and classes, are: 

Why is it with Ruby open source developers not supporting the most common
hosting solution on the net (shared hosting)? 

In my experience 90% of all web projects could very well use a average
shared hosting service (=web hotel) in terms of bandwidth, memory or
database usage.

Are these guys too "pro" to write software thats not running on a
dedicated server? (lol) Or is it just too difficult for them to get it all
working as fast and small as needed? Or is it all just a javanile
inferiority? :p joking here

Well, may be the solutions are out there, and I am barking up the wrong
tree. The search goes on, thanks for the leads, I hope I can contribute my
findings on this forum.

TW