create_symlink is probably the safest, because you want to make sure all of your config files have been pushed and migrations run. If you use update_code and your rake invokes the environment before configs and migrations you could get an error from the rails stack that has nothing to do with assets.
Best to tackle the actual reason it's failing rather than change the hook. For that unless it's actually related to capistrano you should ask in the jammit forums. I use the standard rails 3 asset pipeline so I can't help with jammit. On Jul 31, 2012, at 1:28 AM, ffjia <[email protected]> wrote: > Hi there, > > In many online documents/blogs, it is recommended to run task to minify and > bundle assets using "jammit" after "deploy:create_symlink" [0]. > > But, for some reasons, jammit task may fail, this way, end users will see 404 > errors. Is it better to run jammit before "deploy:create_symlink"? > > Thanks. > > > [0] http://afreshcup.com/home/2010/1/18/notes-on-using-jammit-with-rails.html > -- > * 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 -- * 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
