Eric Armstrong wrote:
> That sounds like a terrific project, well worth pursuing.
> And I am /delighted/ to hear that there are aspects of
> Rails I can use without a database (thanks, Asenchi).
> 
> Thinking I had to install a database is one of the things
> that has kept me from taking a look at Rails...
> 
Even if you do find you need a database eventually, you should take a 
look at sqlite (if you haven't already).  Drop dead simple, especially 
with Rails' migrations.

-- 
Alex

> Mat Schaffer wrote:
>> On Jun 7, 2006, at 9:51 AM, Asenchi wrote:
>>> On 6/7/06, Mat Schaffer <schapht / gmail.com> wrote:
>>>> On Jun 7, 2006, at 12:30 AM, rahul benegal wrote:
>>>> > cameron.matheson wrote:
>>>> >> Hi guys,
>>>> >>
>>>> >> I need to make some simple web-pages at work for internal use
>>>> >> (changing svn password, modifying postfix email-aliases, etc).  I'd
>>>> >> like to use ruby for this.
>>>> >
>>>> > I too am unable to find any documentation or help for building wep
>>>> > apps
>>>> > (*outside* of rails). I am confused between mod_ruby, cgi, fcgi,
>>>> > ruby-web, ruby-fcgi etc. <b>Is there a simple tutorial?</b>
>>>> >
>>>> > I did get a simple cgi program to run off apache (unmodified), but
>>>> > when
>>>> > i added "require 'cgi' it threw a 500 internal error. I have 
>>>> installed
>>>> > rails, but first wish to do some *non-db* stuff outside of it. Just
>>>> > apache or lighttpd.
>>>>
>>>> I've come up against the lack of tutorials for such a thing as well.
>>>> But recently I've made good progress getting mod_ruby and eRuby
>>>> working together to produce a lightweight web environment much like
>>>> PHP (where I came to Ruby from).   Althought I understand mod_ruby
>>>> has some speed issues.
>>>> However, get, post, and cookies are still a bit of a headache.  I'm
>>>> hoping to make some progress on that shortly.
>>>> -Mat
>>>
>>> I've used Rails so much, that now I just install Rails, and use it
>>> without a database.  I really like the whole environment and since I
>>> am used to it (testing, webrick while designing, etc.) it works really
>>> well.  Just a suggestion.  Good luck.
>>
>> I've considered this option as well and I kinda like it.  My main 
>> drive for creating a PHP-like Ruby web environment is evangelism, I 
>> think.  Lowering the barrier to entry so that (so long as it's 
>> installed on the server) all a user has to do to start coding is open 
>> a .rhtml file.  That and possibly pairing it with a PHP->Ruby 
>> translation package to get my old apps working in Ruby (albeit, ugly 
>> Ruby).
>>
>> Hopefully I'm not grossing out anyone too much here, but _I_ think 
>> it's worthwhile.
>> -Mat
>>
>>
>