I don't know. If I call cap deploy:migrations, it will call the methods as above on a release number that is the current time but it gets its own folder in the releases directory. So it looks like its creating a new release with the current time stamp.
On Mar 2, 8:30 pm, Lee Hambley <[email protected]> wrote: > You of course have to commit, and make sure it's pushed (if memory serves, > they are one operation in SVN, right?) > > I daresay that maybe `20100302172844` is not the latest_release, but rather > the current time that you are running this? > > -- Lee Hambley > > Twitter: @leehambley | @capistranorb > Blog:http://lee.hambley.name/ > Working with Rails:http://is.gd/1s5W1 > > On 2 March 2010 20:02, Colin <[email protected]> wrote: > > > > > It's from running cap deploy:migrations. > > > Maybe my methodology is wrong though. If I check a new migration into > > svn (that I have run on my dev database), what should I call to get it > > to run on my prod database? > > > On Mar 2, 6:34 pm, Lee Hambley <[email protected]> wrote: > > > Is that output from a fresh deploy, or just running the migrations? > > > > -- Lee Hambley > > > > Twitter: @leehambley | @capistranorb > > > -- > > * 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]<capistrano%2bunsubscr...@googlegrou > > ps.com>For more options, visit this group at > >http://groups.google.com/group/capistrano?hl=en -- * 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
