|
| <prev next> |
Re: How does one avoid a db:migrate in a cold deploy: msg#00191lang.ruby.capistrano.general
Apologies for not being thorough in my search. I see this issue was addressed only recently on Nov. 27th. http://groups.google.com/group/capistrano/browse_thread/thread/386ea91ce8d91107 On Nov 30, 3:35 pm, me <brooh...-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote: > I've got a project for which I'd like to deploy for the first time. > But I see that cap deploy:cold will run db:migration, and I'd like to > avoid having it run migrations. > > How do I suppress that part of the deployment? > > The db I use is not solely used by my app, and I'd like to avoid > having the migration be run on an already-existing database with live > data. |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | How does one avoid a db:migrate in a cold deploy: 00191, me |
|---|---|
| Next by Date: | Re: Capistrano rails app deployment without DB: 00191, me |
| Previous by Thread: | How does one avoid a db:migrate in a cold deployi: 00191, me |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |