how to choose ruote storage engine?

[emc_lab]

We are new to ruote and would like to integrate ruote into our rails app directly(not going through ruote-kit). Our first question is which storage engine we should use for our rails application. We are looking for robust platform for business use and easy backup. It seems that redis is a good option (it is also the default storage db on document of "with rails"). Our development is on windows and production on ubuntu. In our previous test with ruote-kit, we have used fsStorgage which seemed easy to use on windows.

Comments are appreciated.

[Doug Bryant]

We've been using https://github.com/jmettraux/ruote-sequel backed by postgres.  Never had an issue with it.

Doug

On Tue, Jun 18, 2013 at 5:09 PM, emc_lab <emcla...@gmail.com> wrote:

We are new to ruote and would like to integrate ruote into our rails app directly(not going through ruote-kit). Our first question is which storage engine we should use for our rails application. We are looking for robust platform for business use and easy backup. It seems that redis is a good option (it is also the default storage db on document of "with rails"). Our development is on windows and production on ubuntu. In our previous test with ruote-kit, we have used fsStorgage which seemed easy to use on windows.

Comments are appreciated.

--
--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to openwfe...@googlegroups.com
to unsubscribe : send email to openwferu-use...@googlegroups.com
more options : http://groups.google.com/group/openwferu-users?hl=en
---
You received this message because you are subscribed to the Google Groups "ruote" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openwferu-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[John Mettraux]

> On Tue, Jun 18, 2013 at 5:09 PM, emc_lab <emcla...@gmail.com> wrote:
>
> > We are new to ruote and would like to integrate ruote into our rails app
> > directly(not going through ruote-kit). Our first question is which storage
> > engine we should use for our rails application. We are looking for robust
> > platform for business use and easy backup. It seems that redis is a good
> > option (it is also the default storage db on document of "with rails"). Our
> > development is on windows and production on ubuntu. In our previous test
> > with ruote-kit, we have used fsStorgage which seemed easy to use on windows.
> >
> > Comments are appreciated.
>

On Tue, Jun 18, 2013 at 05:28:47PM -0400, Doug Bryant wrote:
>
> We've been using https://github.com/jmettraux/ruote-sequel backed by
> postgres. Never had an issue with it.

Hello Emclab and Doug,

I'd recommend against using Windows ;-)

You should go with the DB and platform you're most used to. When doing ops
work, I absolutely hate Windows.

Ruote was started in 2006 and since then, it was mostly dev on OSX and prod
on GNu/Linux. Feedback and contributions also followed that pattern.
Windows should be OK, but you'll probably won't get much help when problems
get hairy.


Best regards,

--
John Mettraux - http://lambda.io/jmettraux

[emc_lab]

John,

We are currently using sqlite3 for our rails app db. If using ruote-sequel, can we use the same slite3 db (for rails) as the ruote storage as well (should be single table documents).

Our production env is ubuntu and development is in windows.

Best Regards
-emclab

[Doug Bryant]

Windows 3.1 got me into linux :-)  It drove me to find a better way.

[John Mettraux]

On Tue, Jun 18, 2013 at 08:55:36PM -0700, emc_lab wrote:
>
> We are currently using sqlite3 for our rails app db. If using ruote-sequel,
> can we use the same slite3 db (for rails) as the ruote storage as well
> (should be single table documents).
>
> Our production env is ubuntu and development is in windows.

These days, I run a Debian GNU/Linux in a virtualbox on the Windows7 machine
I use as a VB dev.

Cheers,

[emc_lab]

Very interesting. We are going to try sqlite3 which is db used in our rails app.

[Henry H]

sqlite3 is a poor choice if you're going to have have more than one process modifying the database since it will lock the entire database for each write...