ok...I browsed across some gems and found this: https://github.com/mattconnolly/rails-backup-migrate .....this helps in dumping the whole database in a single file which can then be restored. Let me know if it works in your case
On Wed, Apr 18, 2012 at 1:53 PM, Kal <calcr...@gmail.com> wrote: > Thanks Much Aash, > > But as someone already replied: > > "It only creates tables, but how to transfer data from these tables? > And I think It is same that rake db:migrate RAILS_ENV=production" > > I've gotten as far as "rake db:migrate RAILS_ENV=production" from my > research thus far... > > Seriously, there's no official document for a "Standard" way of doing > this? > > Cheers, > > ~Kal > > > On Apr 18, 3:14 am, aash dhariya <aash.disco...@gmail.com> wrote: > > http://stackoverflow.com/questions/7291381/rails-how-to-migrate-data-... > > may be helpful to migrate from development to production. > > > > > > > > > > > > > > > > On Wed, Apr 18, 2012 at 12:29 PM, Kal <calcr...@gmail.com> wrote: > > > Thanks Hassan, > > > > > This is exactly what I don't get! > > > > > The "Development" environment is the default environment in Rails, > > > yes? > > > > > Now, that means my data is contained in development.sqlite3 and 'rails > > > server' starts WEBrick and so we can view the site from > > >www.homepage.com:3000. > > > > > The step after this is precisely what I'm missing... because nobody > > > talks about it... all the books and guides pretty much stop short of > > > this... > > > > > So this is my question: How do I move everything to the "production > > > environment". I'd imagine that is the ultimate goal, is it not? > > > > > How do I copy the data to production.sqlite3 (just issue: rake > > > db:migrate RAILS_ENV=production) and have all the code (which I > > > created in the Development Env) working in the "Production" > > > environment so it doesn't have to be served out using WEBRick. > > > > > Thanks Much, > > > > > ~Kal > > > > > It's just a test app. However, my plan is to deploy a web application > > > on a public website... someday :) > > > > > > --------------------------------------------------------------------------------------------------------------- > > > > > By the way, I'm running: > > > > > Ruby 1.9.3p0 > > > Rails 3.1.3 > > > Phusion Passenger version 3.0.11 > > > CentOS release 5.6 > > > Server version: Apache/2.2.3 > > > > > ---------------------------------------------- > > > > > On Apr 18, 2:42 am, Hassan Schroeder <hassan.schroe...@gmail.com> > > > wrote: > > > > /* sorry for the near-empty response - fat-fingered it */ > > > > > > On Tue, Apr 17, 2012 at 10:05 PM, Kal <calcr...@gmail.com> wrote: > > > > > Why "bundle execute"? What does that do? > > > > > > `bundle exec` runs your app with the gems specifically described in > > > > your Gemfile. > > > > > > > I don't mean database instance. I mean a scenario where I'm using > > > > > Sqlite3 application for both Development and Production. > > > > > > Probably still not a great idea unless the production instance will > > > > be very lightly loaded. > > > > > > > By "push out", I mean after you've finished the application > > > > > development (which can be viewed using port 3000), how do we then > > > > > "migrate" the finished production into production? > > > > > > What exactly do you mean by "production"? Is this an Intranet app > > > > for your company, an application for a wide Internet public, or ____? > > > > > > If it's a public app, you need to decide on hosting; there's a range > of > > > > options, from having your own server in a datacenter to using a cloud > > > > provider like AWS or Heroku. If it's company-internal, you still > need a > > > > server, but the options may be more limited :-) > > > > > > That's a decision that's only slightly related to Rails, though. > > > > > > -- > > > > Hassan Schroeder ------------------------ hassan.schroe... > > > @gmail.comhttp://about.me/hassanschroeder > > > > twitter: @hassan > > > > > -- > > > 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. > > -- > 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. > > -- 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.
