A blog about software by Alexander Yaäkov Garber.

Rails Study, Day 4: Still Working on the Dev Environment

Published on 29 Mar 2017 by Alexander Garber
So far I have spent time on the following:

  1. Vagrant
  2. Docker
  3. Digital Ocean Droplet
  4. Heroku
However, I'm going to take a step back and reconsider what I'm trying to accomplish.

What is my deliverable?

I want to build a Rails site, hosted on Heroku, that showcases my solutions to puzzles from Advent of Code.

How is my work supposed to flow?

Images, containers, Atom, etc.
  1. Development environment (DE) is separate from the host operating system. (Docker container or VM)
  2. Text editor (Atom) has read/write access to the code in the DE.
  3. The DE can be easily duplicated for a sandbox server.
  4. Code from the DE can be pushed to Github; from Github, the latest code cloned.
  5. Changes from the DE can be pushed to Docker Hub; from DH the latest version of the DE.
  6. Production code from the DE can be pushed to Heroku; from Heroku, the latest production code, although that should be available in Github.

What are the specifications of my development environment?


  1. Version control of all relevant packages.
  2. Read/Write access to development environment from host.
  3. Access to online platform (Github, 
  4. Available locally, without a constant internet connection.
  5. Totally accessible by Atom text editor on my host machine.
  6. Can upload code to Heroku, pull the latest code from Heroku, and push updated code to Heroku.
  7. Can push updates to the environment to a repository.

What shall be my development environment?

  1. Docker container for the DE, with all the necessary packages installed.
  2. Atom text editor installed on host.
  3. FTP access between DE and host.
  4. Github access from DE.
  5. Docker Hub access from DE.
  6. Heroku access from DE.

related posts