Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
From PHP to Ruby on Rails

You're reading from   From PHP to Ruby on Rails Transition from PHP to Ruby by leveraging your existing backend programming knowledge

Arrow left icon
Product type Paperback
Published in Dec 2023
Publisher Packt
ISBN-13 9781804610091
Length 244 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Bernard Pineda Bernard Pineda
Author Profile Icon Bernard Pineda
Bernard Pineda
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Part 1:From PHP to Ruby Basics
2. Chapter 1: Understanding the Ruby Mindset and Culture FREE CHAPTER 3. Chapter 2: Setting Up Our Local Environment 4. Chapter 3: Comparing Basic Ruby Syntax to PHP 5. Chapter 4: Ruby Scripting versus PHP Scripting 6. Chapter 5: Libraries and Class Syntax 7. Chapter 6: Debugging Ruby 8. Part 2:Ruby and the Web
9. Chapter 7: Understanding Convention over Configuration 10. Chapter 8: Models, DBs, and Active Record 11. Chapter 9: Bringing It All Together 12. Chapter 10: Considerations for Hosting Rails Applications versus PHP Applications 13. Index 14. Other Books You May Enjoy

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image