Hello all,
When we deploy, we sure need to syncronize files and folders but,
sometimes, we have this scenario:
a) We develop a database structure and it goes to production.
b) Later we notice that the structure needs to be changed so we change
it locally.
c) We need to update the production structure, however, since it has
been on the production side, we need to preserve the data intact.
I'm not sure what of this could be capistrano work and, what of this
could be MySQL work.
Where can I see some examples about mysql syncronization for a non-rails
application?
According to what I've read we will not use migrate.
I also believe that we can avoid |config/database.yml| .
But, the closest example that I found about this was:
http://www.snippetstash.com/public/9
A lot of lines are not commented and I'm not really getting what is
essential, and what is not, as well as the other ommitted informations,
like: "where exactly should those {variables} be stored etc...
Anyway, I would prefer to forget about that example, and try to see
another much more simpler.
Can anyone give me a hand here and drop a few example lines that I can
probably study, ask, customize and use ?
Thanks in advance,
Márcio
--
* 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