Márcio, Where can I see some examples about mysql syncronization for a non-rails > application?
Rails uses a migrations syntax, in a nut-shell, this works like 001-create-table-one.rb, 002-create-table-two.rb, 003-change-table-one.rb, each one is tracked, and if `003` hasn't been run, it gets run… that's all there is to it, they don't preserve data (unless you write them carefully) and it's not a MySQL feature or something. The Rails method works across databes… supporting MySQL, PostgreSQL, etc.. it's a pretty naïve implementation, but it works well. Perhaps your framework gives you something, if not you might want to look at `cap web:disable` and `cap web:enable` - to (also naïeve) tasks for copying a template "maintenance" page into place whilst you do work that requires some downtime (or a few minutes on a quiet DB) Regarding assets between deploys, there's a variable called :shared_children - you set it to an array of the `shared between release` directories, this defaults to something like log, config, tmp, etc - these are documented here: https://github.com/capistrano/capistrano/blob/master/lib/capistrano/recipes/deploy.rb#L50 Put whatever directories you need in here, then at first/early deploy time, make sure your assets are in :deploy_to/shared/whatever-directory/ Hope that helps, at least a little (focused questions are more likely to elicit answers out of reluctant mailing list subscribers!). -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
