Rails Dev Environment Setup

  1. Development Environment
  2. Packages & Dependencies

 

 

Before we can build our app, we need a suitable environment to work in - this will generally take the form of either some kind of virtual machine or using Docker. There are a number of ways we can get this set up depending on your local workstation’s resources and how you prefer to work:

  • One of the easier / less resource intensive options will be to use an online IDE, meaning you won’t have to host anything on your local machine. I quite like https://codeanywhere.com/, which you can use your Google account to access for free (because you definitely have a Google account, don't you?).
    Once signed up and on your Dashboard click New Container, give it a name and search for the Ruby stack, select it and hit OK.

  • My overall recommended option for new starters is to start from scratch and create a virtual machine of a nicer Linux distribution - Ubuntu being a prime recommendation. Your workstation will need to be packing a little bit of muscle to make this work, but it will allow you to develop your application in a contained environment.
    Simply install a VM client (such as Virtualbox) on your local machine and download a .iso file for the latest LTS Ubuntu release (22.04 at time of writing, available here). When you start the VM it will ask you for the file path of the .iso file, after which the installer wizard will start and you just need to follow its instructions.

  • Alternatively you fancy a bit more of a challenge but don’t have the computing power necessary to run your own local VM. You can therefore use your Google account again to spin one up in Google Compute Engine (GCE). The trial for this platform gives you $300 of resource to use over 90 days, which is more than enough to complete this and have a bit of a play afterwards - just make sure you turn the machine off when it isn’t in use!
    This blog also contains a handy little guide to get yourself set up with a GCE VM, which you can view here.

  • An alternative option if you are already running a Linux workstation is to develop and run your app directly on your machine. This is not something I would generally recommend, but is an available option in pinch if you're just running a geriatric laptop.

  • Possibly the most advanced option will be creating your application inside a Docker container and using docker-compose to develop inside it from your own workstation. This has many benefits, marrying the convenience of developing on your workstation with the safety of an sandboxed environment similar to a VM.
    This is not recommended for absolute beginners. However, if you are experienced, interested and / or brave enough, my instructions on how to set this up can be found here.

For the purposes of this guide, we will start by developing our web app inside a VM running Ubuntu 22.04 until it reaches a point of reasonable usability and beauty. Once this is complete and you hopefully have a bit of confidence in your abilities, we will go through how to Dockerise our application (this is how I learned, if that wasn't obvious).

 

 

Once your basic VM is up and running and the OS is installed, we’ll need to make sure it is up-to-date with the latest base packages and then install the new packages we need to actually develop our Rails app:

  • Ensure you have all repositories enabled in apt - your /etc/apt/sources.list should look something like: 

    /etc/apt/sources.list
    
deb http://archive.ubuntu.com/ubuntu/ jammy main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse
deb http://archive.canonical.com/ubuntu jammy partner
deb http://security.ubuntu.com/ubuntu jammy-security main restricted universe multiverse

  • Now update the apt cache to include these repos and upgrade our base packages: 

    $ sudo apt update       ## refresh packages in cache, identify which available to upgrade
$ sudo apt upgrade -y   ## grab updated versions of already installed packages

  • With this done we’re ready to grab the packages we need to develop: 

    $ sudo apt install git-core curl build-essential openssh-client  ## version mgmt and other essentials
$ sudo apt install ruby ruby-dev                                 ## guide built with v3.3.0
$ sudo gem install rails                                         ## guide built with ‘-v 7.1.3.2’
$ sudo apt install libsqlite3-dev sqlite3 postgresql libpq-dev   ## database dependencies
$ sudo apt install ruby-bundler nodejs npm g++ yarn yarnpkg      ## ruby gems & JS dependencies
$ sudo npm install --global n yarn                               ## need node’s version manager and yarn release

 

 

With this all set up, we are now essentially ready to get started. However before we dive in, there is just one more thing we need to get configured that is arguably as important as the app itself; version control.

 
 

< Rails Application Overview | Version Control >
Back

Comments

Post a Comment

Popular posts from this blog

New Rails Apps with Docker Compose

Image
Following on from the Docker & docker-compose guides, it is possible to use docker-compose to build a Rails application that uses a PostgreSQL database without even installing Ruby on your local machine by instead using containers ! This becomes a very useful option to have if you work from many different workstations and don't want to ensure they are all equipped with the correct Ruby and Rails dependencies, or if you wish to use a version of Ruby / Rails not supported by your operating system (for example, Ubuntu 20.04 only allows provides up to Ruby 2.7 in its apt cache). In fact, Rails 7 added native support for Docker, such that it generates almost all of the default files we need for us! This comes with its problems and, I won't lie, updating this post to work with Rails 7 (it was previously written for Rails 6) has been a colossal pain and features a bit of hackery. However it is ultimately a good thing, and having
Read more

[ToDoList] Basic Pages

Image
Well that was fun. However all we’ve really done is spooked someone called Bob, without actually creating anything remotely resembling a web application. Let’s rectify this and create some pages one would normally find on a website; a Home page and an About page. Home & Away About Helpful Links [Insert Beatles Reference]     Because we already learned a bit about MVC, we know that we will need a controller and at least one view to display these pages (we won’t need to worry about models until we’re handling real data). As before, we’ll need to add a route configuration so Rails knows where to go, too. Rails provides a fair bit of magic to streamline this process in the form of generators . However, because we’re learning, we’re going to do this manually for now and learn what this magic entails, so we can appreciate it more later. We already created a PagesController in the last sec
Read more

[ToDoList] Docker Compose

Image
We learned in the previous section how Docker is a fantastic tool with which to build and deploy applications, however has some inconveniences with developing these apps such as having to rebuild the image every time there is a code change as well as any development database entries being wiped. This section will offer some relief against these two issues by using Docker Compose to build our application and make live code changes, as well as using a separate container to host our development database in PostgreSQL - this will encompass three main tasks: Back up and edit the Dockerfile we made in the previous section so our image can be built. Create our docker-compose.yml in the app's root directory to create our web & postgresql database containers. Back up and edit some our app's configuration (namely the database.yml & Gemfile ) to use the new postgresql container . After all this, we can set about
Read more