Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

General Discussion

Kevin Korte
Kevin Korte
28,149 Points

Upgrading applications built on frameworks like Laravel or Rails.

Quick question for my developer savvy friends. Been learning Laravel and Rails side by side, compare and contrast almost. I am more familiar with PHP, and thus Laravel is naturally more fluent to me, but Rails has me in a honeymoon phase with how intelligent it is.

With that said, I know that Rails goes through regular updates, and I know that for instance the lessons on Laravel here are on V4, but currently Laravel is on V5, and there were some fairly significant differences that I had to figure out on my own compared to the videos.

I know the answer to this question must be a fairly practical answer, but for either framework or both, how important is it to update your application after the a new version of the framework comes out? Can you not do the update until you want a feature that is part of the newest update? And when you do start the update, is it something that can usually be completed in a few hours, or even a few days? Basic re-factoring of the code to ensure you're following the newest version's conventions?

And finally, I imagine that ensuring you stay up to date enough that the framework is current with the language it is using (PHP or Ruby) and that version of the language is supported by your host, is an important reason to stay current, but how fast does this process move along?

Thank you to all that help me understand this part of the process.

1 Answer

depends on how big your site is & how complicated it is. if i had a site using v4, i would copy it to a new url (subdomain would do!). upgrade to v5 & then test there first.

i like laravel but from v3 - v5 there has been significat chnges in each version... :(

Kevin Korte
Kevin Korte
28,149 Points

I've noticed that with Laravel. I'm more comfortable right now with that. I did the Laravel course here, which was done in V4, but I built a long in V5. I was able to use Laravel's docs to follow along in V5 when it was different than the video, which was surprising a lot.

As far as complication goes, not bad. I just can't find and likely won't find a CMS to create and manage data how I need. Mostly I need to attach a data value to a post. Each data value can and likely will be attached to multiple posts, and each posts will have multiple data values.

I appreciate the response. I'll keep learning each and see what happens. I do like the idea of a subdomain to test. Thank you for that.