Book Image

From PHP to Ruby on Rails

By : Bernard Pineda
4 (1)
Book Image

From PHP to Ruby on Rails

4 (1)
By: Bernard Pineda

Overview of this book

Are you a PHP developer looking to take your first steps into the world of Ruby development? From PHP to Ruby on Rails will help you leverage your existing knowledge to gain expertise in Ruby on Rails. With a focus on bridging the gap between PHP and Ruby, this guide will help you develop the Ruby mindset, set up your local environment, grasp the syntax, master scripting, explore popular Ruby frameworks, and find out about libraries and gems. This book offers a unique take on Ruby from the perspective of a seasoned PHP developer who initially refused to learn other technologies, but never looked back after taking the leap. As such, it teaches with a language-agnostic approach that will help you feel at home in any programming language without learning everything from scratch. This approach will help you avoid common mistakes such as writing Ruby as if it were PHP and increase your understanding of the programming ecosystem as a whole. By the end of this book, you'll have gained a solid understanding of Ruby, its ecosystem, and how it compares to PHP, enabling you to build robust and scalable applications using Ruby on Rails.
Table of Contents (15 chapters)
1
Part 1:From PHP to Ruby Basics
8
Part 2:Ruby and the Web

MVC at its finest

As mentioned previously, Rails is an MVC controller. If you’ve used PHP frameworks in the past, such as CodeIgniter, Symfony, or Laravel, you will probably be familiar with the term. If you’re not, I recommend checking out these pages:

  • https://www.oracle.com/technical-resources/articles/java/java-se-app-design-with-mvc.html
  • https://pusher.com/blog/laravel-mvc-use/#why-use-mvc

In summary, the MVC pattern divides our application into three components – the model, in which we save all of our business logic (mostly but not exclusively by connecting to a database), the view, in which we hold what is to be shown on the browser (HTML for the most part), and the controller, which serves as the organizer of the previous two. If we were to use an example to explain this, a user authentication component would function as follows: the HTML form that shows the user and password fields would be created on the view. Once the user clicks on...