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

Gemfile versus composer.json

As I mentioned before, bundler helps us handle all our program’s dependencies – that is, everything we need to install in order for our program to run correctly. To accomplish this, bundler uses a text file, which we will call a Gemfile. Composer works in a very similar way by having us create a file called composer.json, but while Composer downloads the required libraries into a folder, bundler installs them on our system. If bundler determines that a dependency is missing, it will automatically try to install it. Ruby’s way is a bit more magical (or automatic). Let’s take bundler for a test drive to understand the process a little further. We will start by uninstalling our previously installed oj gem with the following command in the shell:

gem uninstall oj

The preceding command will confirm when the gem is removed from our system:

Successfully uninstalled oj-3.14.2

Now, if we try to run our reading_json.rb again...