Hey all,
I’m got my new production server (Debian) up and running with Lighttpd
and
am now trying to get RadiantCMS working. If I try to just run
“scripts/server lighttpd” it rails saying that Lighttpd is not installed
on
my system (or not in my path). Lighttpd most certainly is installed on
my
system and it’s running just fine. However I don’t think I want Radiant
to
“run” my webserver. How can I just make it use the already existing
Lighttpd instance? I think I could have Radiant start up Mongrel and
then
point Lightthpd to that, but that is quite a lot of moving parts just
for a
simple web app. Is there a “scripts/server standalone” option or
something?
Thanx!
Richard
The typical solution with lighttpd is to use FCGI. You can configure
lighttpd to either spawn Radiant FCGI processes, or you can start/stop
them yourself with script/process/spawner and script/process/reaper.
Mongrel is not necessary.
Sean
As Sean as pointed, rails apps are served by lighttpd through fcgi. All
you need to do is setup lighttpd.conf correctly. These two links are
useful:
http://duncandavidson.com/archives/153
http://textsnippets.com/posts/show/70
/AITOR
Ok, so I’m a little quick on the draw. Shutting everything down
completely (read: lighttpd) and starting up fresh worked great. At
least I
can log in. I’ll play with it and see if it breaks and see what kind of
speed I can get out of this thing.
Later…
Richard
Lighttpd and sqlite3 are not related, sqlite/sqlite3 is not compiled
inside lighttpd. If you still have problems it could be the common
problem
with sqlite3 & rails:
http://wiki.radiantcms.org/FAQ
A tuned MySQL/Postgre should be faster than sqlite3, but sqlite3 has
some administration advantages.
/AITOR
WooHoo, I got it working. However, it looks like there is a problem
with
Lighttpd & SQLite3 on Debian stable. Apparently Lighttpd is compiled
against SQLite instead of SQLite3 and I’m getting all kinds of weird SQL
errors:
ActiveRecord::StatementInvalid (SQLite3::SQLException: SQL logic error
or
missing database: INSERT INTO sessions (“updated_at”, “session_id”,
“data”)
VALUES(‘2007-10-09 17:24:02’, ‘90ade8e8a03b57f98e3b4ffa55c094f4’,
'BAh7BiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNo
SGFzaHsABjoKQHVzZWR7AA==
')):
This same exact setup works when run against a Postgres database, so I’m
thinking it’s a SQLite3 library thing. Any suggestions? I like
Postgres
and might just keep using it but the simplicity of SQLite3 just makes me
weep for joy. 
Also, I am curious about the performance differences
between the two DBMSs. It seems like SQLite3 should perform better for
smaller sites (as long as you can keep the db file in memory). What do
you
think?
Thanx!
Richard