I'll help you with the database end a little. This example takes into account the following:
I have two production servers - linux server A, and linux server B. I have one development windows box - dev box C. All three use MySql for database handling. I have putty installed locally. The first thing I do is I set the port for dev box C to something other than 3306. In this case my dev box C can act as the staging server. I set the port to 3400. Server A is the server I want the new data to go to and Server B houses the data I want to retrieve. I open Putty and go to tunnelling and activate it with SSH. I open Server B with Putty and now tunnelling is active. At this point, if I open an instance of MySql with port 3306 it will locally connect to Server B securely through SSH. This allows you to not use remote DB handlers. At the same time, I have port 3400 open as a connection with MySql. I now can operate two database instances simultaneously. >From here, you can do quite a few things. You could easily send development data to the localhost:3306 connection from localhost:3400 using Rails. You could also use capistrano for performing mysql data dumps as well: http://codesnippets.joyent.com/posts/show/1215. If you want to transparently work with your second database from here, you could use this gem: https://github.com/karledurante/secondbase. I hope some of the information helps. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
