자산이 공급되고 있는지 확인하십시오! 앱에 302가 발생 했으므로 라우팅이나 애셋이이를 수행하고있을 수 있습니다.
나는 이미이 볼 수도 알고 있지만, 다음에 체크리스트를 수행합니다 3.0
[ ] git checkout -b oh-noes-here-we-goes
[ ] Use the Rails 3.0 upgrade tool RailsCast to overwrite your current application
[ ] Get your Gemfile in order, attempting to load rails console as you go
[ ] Update your ActiveRecord queries to the new syntax
[ ] Loading rails console is a huge deal: Have a {chocolate,whiskey,beers}
[ ] Let's run that test suite. If you're test unit: yay! If you're rspec, upgrade! (probably best to delete spec/helper and rails g rspec:install
[ ] run your javascript tests (hahahahaha omg I know right?!?!!!)
[ ] If your pages load, that means you have a somewhat functioning rails 3.0 application. Commit your changes and get it on heroku for your staff/helpers/friends&family to go to
[ ] Let's talk about Authentication. Don't continue to run acts_as_authenticatable or auth_modules just because its there. My recommendation: replace with devise and send your users a link to reset their password. This is controversial, as your users will know something's up… but: something IS up, you're not as secure as you need to be
[ ] Update your mailers to the new syntax (and add tests to cover this case)
3.2
레일을 얻기 레일에
http://www.rails-upgrade-checklist.com/#3.0
방법 :
소스가
[ ] upgrade your gem file to 3.2.13
[ ] Add these gems to your Gemfile under a new "assets group"
[ ] Move your public/images to app/assets/images
[ ] Move your public/stylesheets to app/assets/stylesheets
[ ] Move your public/javascripts to app/assets/javascripts
[ ] Go through your stylesheets and look for urls(); if local, replace with image-url() (Sass)
[ ] Remove any layouts that individually call stylesheets and javascripts
[ ] See if your pages start to break open and swallow you whole
[ ] Remove jQuery
[ ] move your JavaScript libs (underscore, etc) to vendor/assets
[ ] build your application.scss and application.js --- don't put code in these files, just require other files (or load the entire tree)
[ ] find the problems when you're loading every CSS and JS on every page --- it's very common and you might need to change your application to be nicer
[ ] Use RailsDiff to identify additional required configuration changes
[ ] commit and push to heroku. do a little dance if it loads. ask for feedback
다른 사람이 다른 문제가있어서 R 괴롭히는 보석 업그레이드 : 다른 모든 실패, 체크 아웃 rbates하면
How to upgrade Rails app from 2.3.5 to 3.2.x?
:
http://railscasts.com/episodes/282-upgrading-to-rails-3-1
너무 적은 정보를 제공합니다. –
@mohit보기 파일을 표시 하시겠습니까? – uday
'curl -v http : // localhost : 3000'의 결과는 무엇입니까? –