what are the steps to follow for migrating a project from rails 3.2.13,ruby 1.9.1 to rails 4.2 or rails 4 other versions? -


i have project on rails3.2.13 , having around 80 gems in it,now need migrate project rails 4,what steps need follow upgrading without gems conflicts , errors.

with many gems in codebase suspect large app , not going quick upgrade , unless have been given large amount of time this, best bet break things down , updates in stages on old version , upgrade when feel codebase in better state.

before attempting upgrade consider these points , make small changes / releases before big upgrade project. less code have change @ final upgrade stage less risks have.

  • gems: more gems have, more code have worry , more more code have upgrade. app using these gems , if not can remove un-used ones. of gems pretty basic , can same functionality rails / ruby functionality , remove gem altogether. less gems have, less pain have when comes upgrading.
  • tests: whilst working on code, write tests new code add or alter , write tests core parts of code.
  • latest 3.2 release: coebase running on latest 3.2 release, include warnings of things may not work can sort out sooner.
  • deprecated: there deprecated warnings in logs, if fix these before attempting upgrade.
  • old code: there code know wont work on later versions, can replaced work on both.

when feel codebase in state can upgraded, consider these points.

  • i suggest not trying @ same time: think breaking out ruby upgrade separate project rails upgrade.
  • maybe consider moving slowly, getting app onto 4.0 or 4.1 , re-evaluating things using points above prevent less risk things breaking.
  • regardless of how many automated tests have, software tester run on app. find errors automated tests have missed.

there plenty of upgrade guides out there should take read of before performing upgrade.

good luck.


Comments

Post a Comment

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

i'm trying link specific pdf page msoutlook'10 or msword'10, #page=... anchor particularly useful , works fine elsewhere. unfortunately when click [ctr-k] in outlook or winword, links re-formatted assuming unc path. pdf file located on shared drive. using "file:" prefix links open pdf in adobe reader (outside of browser), , "http:" open inside browser. issue seem need open in browser "file:" prefix in order anchor work. know anchors work inside browser. outlook uses windows/explorer default program (based on file extension) seems open in adobe reader neglecting anchor. is aware of solution, link specific page or bookmark of shared-pdf ms outlook and/or winword link? common references: mailermailer.com/...anchor-tags-html-emails campaignmonitor.com/...anchor-links-in-email-newsletters/ stackoverflow.com/...anchor-in-pdf-document
Read more

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

consider code: test = function() { } t = new test(); (var = 0; < 8; i++) { result = t instanceof test; } if change number of iterations 8 9 , loop take 100 times longer complete in latest version of firefox (41.0.1). tested on 2 different pcs , magic limit 8. here jsperf test used: http://jsperf.com/instanceof-8-times-vs-9-times does have idea why might happen? seems specific instanceof . not happen if else object, example check property. note: filed bugzilla bug this. jan de mooij mozilla team has posted details in bugzilla thread . here's simplistic interpretation of highly technical answers: in i < 8 case, firefox smart enough hoist result = t instanceof test; statement out of loop (according tests, doesn't seem omit altogether). in i < 9 case, apparently doesn't optimization . why? reason not clear, related fact 9 iterations threshold above function considered "hot" enough run through jit compiler. i < 8 cas...
Read more

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -

following this guide setup app on digital ocean droplet, not working. site not loading , it's throwing: "gateway time-out". the puma server works, since ps aux | grep puma prints: root 15878 0.0 0.4 376832 2168 ? sl 12:50 0:00 puma 2.13.4 (unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock) [20150930164940] root 15881 0.0 0.7 903676 3692 ? sl 12:50 0:06 puma: cluster worker 0: 15878 [20150930164940] root 24654 0.0 0.1 11748 916 pts/2 s+ 18:00 0:00 grep --color=auto puma my nginx config: user root; worker_processes 1; events { worker_connections 1024; } http { upstream puma { server unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock; } server { listen 80; server_name myapp.com; root /var/www/myapp/current/public; access_log /var/www/myapp/current/log/access.log; error_log /...
Read more