I hope this helps somewhat.
Raul
The one you already know!
> and what is the best databse for rails project ?
I've been a fan of MySQL for a couple of years now, performance is good,
and now it has a BIG industry gorilla behind it.
This is a good question for your system administrator. It's whatever
you/they fill the most comfortable with maintaining.
> and what is the best databse for rails project ?
PostgreSQL. There is a huge *community* behind it... kind of like Ruby
and Rails. ;-)
Cheers,
Robby
--
Robby Russell
Founder and Executive Director
PLANET ARGON, LLC
Design, Development, and Hosting with Ruby on Rails
http://www.planetargon.com/
http://www.robbyonrails.com/
aim: planetargon
+1 503 445 2457
+1 877 55 ARGON [toll free]
+1 815 642 4068 [fax]
> what is the best linux version for rails project ?
upto my knowledge Ubuntu is doing good with updates, communities and
forums
> and what is the best databse for rails project ?
in case of database it is MYSQL..
Mahalingam
Sr.Sys.Admin
Railsfactory
I'll agree with this, but throw out my personal preference of Gentoo
linux ;)
>
>
>> and what is the best databse for rails project ?
>
> PostgreSQL. There is a huge *community* behind it... kind of like Ruby
> and Rails. ;-)
And I will agree that postgres is a better database then mysql in
most cases> But I will still choose mysql for one major reason...
replication. Postgres has no built in replication except for WAL file
replication which means the slave is in recovery mode and you cannot
run queries against it. If you are sure that you will never need to
scale past one db server then psql is probably a better choice but if
you will need to scale then mysql beats postgres hands down when it
comes to master, slave and master master replication.
Cheers-
- Ezra Zygmuntowicz
-- Founder & Software Architect
-- ez...@engineyard.com
-- EngineYard.com
>
> And I will agree that postgres is a better database then mysql in
> most cases> But I will still choose mysql for one major reason...
> replication. Postgres has no built in replication except for WAL file
> replication which means the slave is in recovery mode and you cannot
> run queries against it. If you are sure that you will never need to
> scale past one db server then psql is probably a better choice but if
> you will need to scale then mysql beats postgres hands down when it
> comes to master, slave and master master replication.
>
This is excellent to know! Thanks
Raul
Yup, this is a PostgreSQL limitation. Slony is the non-WAL replication
solution, but I hear tell that Slony and Rails (specifically, AR
migrations) don't play so well together either... boo.
That said, I've used PostgreSQL on a bunch of apps and always been happy
with it. I've always kind of figured that if I got a DB that was too
big for one box I'd shard the data or something...
Yours,
Tom
But if you have to have an answer, I would go with latest Debian stable
(4.0 as of now) and PostgreSQL.
We tend to use CentOS (or RHEL if the customer requires a high SLA).
It's got Ruby 1.8.5 and then we install RubyGems from source (I think
the packaged RubyGems version is 0.9 still). Nice thing is that all
major third-party software is guaranteed to work with RHEL (and thus
CentOS), that it doesn't require forced upgrade and has a long support
cycle. And if you're into Xen, well than that's got some amazing backing
too.
Out of the box it comes with PostgreSQL 8.1 which incidentally is our
database server of choice. It's fast (though it requires tuning to get
there), got excellent ACID properties and has never failed on us even
with large datasets. If so required it can do synchronous replication
and parallelization too.
For specialty cases we set up JRuby or hand-compile Ruby 1.8.6.
--
Roderick van Domburg
http://www.nedforce.nl