I have been working in development and am close to go beta in production. Is there a way, in rails, to copy the development database schema to production and initialize with base data? Thanks for any pointers, Long --~--~---------~--~----~------------~-------~--~----~ 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
Look up information about ''migrations'' (which takes care of the schema) and ''bootstrapping'' (which takes care of the data). Some links on Migrations: http://glu.ttono.us/articles/2005/10/27/the-joy-of-migrations http://garrettsnider.backpackit.com/pub/367902 http://rubyonrails.org/api/classes/ActiveRecord/Migration.html I don''t have any links for bootstrapping, but I''m sure if you google ''rails bootstrapping'' you''ll come up with something. If you''re successfully using capistrano, after you set up your schema.rb and migration files on your local machine you do # cap deploy_with_migrations to send the schema out to the production machine. If you''re not using capistrano, I don''t know what to do, but I would guess that if you just upload those schema and migration files and then ssh into the remote machine you could do # rake migrate to update your production schema. I know this is far from a detailed answer but it might point you in the right direction. --~--~---------~--~----~------------~-------~--~----~ 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
> "Jay Jansheski" wrote: > > Look up information about ''migrations'' (which takes care of the schema) > and ''bootstrapping'' (which takes care of the data). > > Some links on Migrations: > > http://glu.ttono.us/articles/2005/10/27/the-joy-of-migrations > http://garrettsnider.backpackit.com/pub/367902 > http://rubyonrails.org/api/classes/ActiveRecord/Migration.html > > I don''t have any links for bootstrapping, but I''m sure if you google > ''rails bootstrapping'' you''ll come up with something. > > If you''re successfully using capistrano, after you set up your > schema.rb and migration files on your local machine you do > > # cap deploy_with_migrations > > to send the schema out to the production machine. If you''re not using > capistrano, I don''t know what to do, but I would guess that if you just > upload those schema and migration files and then ssh into the remote > machine you could do > > # rake migrate > > to update your production schema. I know this is far from a detailed > answer but it might point you in the right direction. >Hi Jay, Excellent links to keep handy! Thanks a bunch. Long --~--~---------~--~----~------------~-------~--~----~ 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---