Switch from Docker to Vagrant

(Big old squashed commit)

Squashed commit of the following:

commit 0bd0380
Author: DeeDeeG <[email protected]>
Date:   Fri Oct 5 20:15:23 2018 -0400

    setup_vagrant: Remove unnecessary packages

    Delete section of unnecessary package installation.

    Does not impact functionality of installation.

commit 2269ce0
Author: DeeDeeG <[email protected]>
Date:   Fri Oct 5 19:29:25 2018 -0400

    setup_vagrant.sh: Idempotentialize PhantomJS config

    Only try to install and configure PhantomJS
    if there is no phantomjs directory in /usr/local/bin.

commit f54773c
Author: DeeDeeG <[email protected]>
Date:   Fri Oct 5 19:23:03 2018 -0400

    Revert "setup_vagrant.sh: Install phantomjs via APT"

    This reverts commit ba85fa3.

    The APT package from the Ubuntu repository has too many
    heavy dependencies. Install just the custom-packaged version.

commit 262a45b
Author: DeeDeeG <[email protected]>
Date:   Fri Oct 5 18:53:17 2018 -0400

    setup_vagrant.sh: Move nodejs package install

    Use the idempotent apt installer subscript to install nodejs.

commit f5d9e1c
Author: DeeDeeG <[email protected]>
Date:   Fri Oct 5 18:50:15 2018 -0400

    setup_vagrant.sh: Idempotentialize Node.js config

    Only try to configure Node.js repo andother settings
    if there is no nodesource.list in /etc/apt/sources.list.d/

commit 54217ad
Author: DeeDeeG <[email protected]>
Date:   Fri Oct 5 18:45:17 2018 -0400

    setup_vagrant.sh: Idempotentialize Yarn repo

    Don't try to add the repo again if yarn.list already exists
    in `/etc/apt/sources.list.d`.

    (Is "idempotentialize" a word?)

commit 47a9cde
Author: DeeDeeG <[email protected]>
Date:   Fri Oct 5 18:30:40 2018 -0400

    setup_vagrant.sh: Install Yarn idempotently

    Use the nice APT idempotent package installer subscript
    to install Yarn. Neatens up the script,
    saves time when re-provisioning.

commit ba85fa3
Author: DeeDeeG <[email protected]>
Date:   Fri Oct 5 18:28:24 2018 -0400

    setup_vagrant.sh: Install phantomjs via APT

    Uses the package from the Ubuntu Bionic repositories,
    instead of custom-installing.

commit 6563c04
Author: DeeDeeG <[email protected]>
Date:   Fri Oct 5 18:24:25 2018 -0400

    setup_vagrant.sh: cleanup top of script

    Rearranges package installations
    under their own headers.

    Much more readable this way.

commit a404866
Author: DeeDeeG <[email protected]>
Date:   Fri Oct 5 17:50:31 2018 -0400

    Use rvm instead of rbenv and ruby-build

    Change setup_vagrant.sh from downloading and compiling ruby
    with rbenv to simply downloading and installing RVM's binary of ruby.

commit 5aafb18
Author: DeeDeeG <[email protected]>
Date:   Fri Oct 5 00:31:30 2018 -0400

    Bump Vagrant setup to 18.04 Bionic

    We need to do this because:
      1) Trusty will be end-of-service soon
      2) rvm does not have latest ruby binaries for Trusty

commit 63bd486
Author: DeeDeeG <[email protected]>
Date:   Thu Oct 4 21:40:52 2018 -0400

    Un-pin bundler; just download the latest version

    Vagrant stopped using bundler internally in late 2016.
    See:
    https://github.com/hashicorp/vagrant/commits/master/vagrant.gemspec

    And these two commits:

    4 Jan 2014, Vagrant begins to use bundler internally:
    hashicorp/vagrant@f2c6175

    5 Sep 2016, Vagrant drops its internal dependency on bundler:
    hashicorp/vagrant@1fb4553

commit a411369
Author: DeeDeeG <[email protected]>
Date:   Thu Oct 4 21:32:06 2018 -0400

    Revert "Docker (RefugeRestrooms#435)"

    This reverts commit 5876b6a.

    (Restores Vagrant configuration as an alternative to Docker.)

.rake/vagrant.rb

@@ -0,0 +1,14 @@
+namespace :vagrant do
+  task :shell, [:command] do |_t, args|
+    fail "Usage rake vagrant:shell[command]" unless args[:command]
+
+    vagrant_path = 'PATH=/home/vagrant/.rbenv/shims:$PATH'
+
+    # We need to reset RUBYLIB in order to use gems in
+    # the context of the VM.
+    #
+    # Please see: https://github.com/mitchellh/vagrant/issues/6158#issuecomment-135796049
+    # for more info.
+    sh "unset RUBYLIB; vagrant ssh -c 'cd /vagrant/ && #{vagrant_path} bundle exec #{args[:command]}'"
+  end
+end

.travis.yml

@@ -2,14 +2,16 @@ env:
   global:
     - CC_TEST_REPORTER_ID=c18df080592f9c99ca8080a6d5e052aa5fd3964044a0fe0b71e48f8e18998dc2
 language: ruby
-services: docker
-before_install:
-  - docker-compose build
+cache: bundler
 before_script:
   - curl -L https://codeclimate.com/downloads/test-reporter/test-reporter-latest-linux-amd64 > ./cc-test-reporter
   - chmod +x ./cc-test-reporter
   - ./cc-test-reporter before-build
 script:
-  - docker-compose run -e "RAILS_ENV=test" web rake db:test:prepare spec
+  - bundle exec rake db:setup RAILS_ENV=test
+  - bundle exec rake db:test:prepare
+  - bundle exec rake spec
+rvm:
+  - 2.3.7
 after_script:
   - ./cc-test-reporter after-build --exit-code $TRAVIS_TEST_RESULT --prefix /refugerestrooms

CONTRIBUTING.md

@@ -5,58 +5,34 @@
 ### 1 Fork and clone the repository.
 https://help.github.com/articles/fork-a-repo/
 
-### 2 Install Docker.
-https://docs.docker.com/install/
-
-### 3 Build the Docker Container
-Build the container from any [terminal](https://github.com/RefugeRestrooms/refugerestrooms/wiki/What-is-a-Terminal-(or-%22Terminal-Emulator%22)%3F-How-do-I-run-text-based-commands-on-my-computer%3F) program with:
-```
-docker-compose build
-```
-
-### 4 Run the Docker Container
-
-You can now run the app with:
-```
-docker-compose up
-```
-
-The container will be reachable at this address: `localhost:3000`
-
-_(Point your web browser at `localhost:3000` or `127.0.0.1:3000`, or even `[IP address of computer running the container]:3000` from any computer on the same LAN. The last method is useful for testing the app/site on smart phones and tablets.)_
-
-### 5 Do some Development
-
-Files are shared between your computer and the Docker machine. If you update a file on your computer, the change should show up on the Docker machine, and vice-versa.
-
-If you need to run commands on the Docker container directly, run this:
-```
-docker-compose run web bash
-```
-_(This will give you a full interactive terminal session running on the Docker machine. You can (for example) run `bundle update` to update the Gems in the Gemfile to more recent versions.)_
-
-Occasionally, you might need to rebuild the Docker machine so it picks up major updates (such as a new version of Ruby, or an updated Gemfile). To do so, run `docker-compose down` and `docker-compose build`.
-
-### 6 Run the Tests
-```
-docker-compose run -e "RAILS_ENV=test" web rake db:test:prepare spec
-```
-_(If you want to know if your changes pass our automated testing, before even submitting your changes to RefugeRestrooms on Github, this will let you know.)_
-
-### 7 Shut down the Docker Container:
-In another terminal window, run:
-```
-docker-compose down
-```
-_(Shutting down the container in this way is safer than exiting with `Ctrl + C` or `Cmd + C`, and prevents issues with breaking the `db` container.)_
-
-### 8 Optional tasks:
-To clean up encoding problems in the safe2pee data, run (Use `rake db:fix_accents[dry_run]` to preview the changes.):
-```
-docker-compose run rake db:fixaccents
-```
-
-### Assets
+### 2 Install Vagrant.
+https://www.vagrantup.com/downloads.html
+
+### 3 Install VirtualBox
+https://www.virtualbox.org/wiki/Downloads
+
+### 4 Capture the powers of vagrant
+  * In the repo dir: <code>vagrant up</code> (Safely ignore: 'dpkg-preconfigure: unable to re-open stdin: No such file or directory')
+  * If changes have been made since running vagrant up: <code>vagrant provision</code>
+
+  * Start the rails server. There are two ways to do this, depending on your familiarity running from within the vagrant shell:
+
+    1. A local `rake` wrapper that allows direct execution on the machine.
+        * Run `rake vagrant:shell[command]`<sup>1</sup>
+        * To start the rails server using the rake wrapper use: `rake vagrant:shell['rails s -b 0.0.0.0']`.
+        * Navigate to `localhost:3000`
+    2. Using `vagrant ssh` to gain access directly to the machine.
+        * To login to the machine: <code>vagrant ssh</code>
+        * `cd  /vagrant/` to navigate to the refuge repo.
+        * To start the rails server use: `rails s -b 0.0.0.0`. 
+        * Navigate to `localhost:3000`
+
+  [1] You can run any command locally using `rake vagrant:shell[]` and it will be executed in the repo root of the vagrant machine. You can try `rake vagrant:shell['pwd']` and see it will print the directory that the repo is in on the vagrant machine!
+
+### 5 Optional tasks:
+run <code>rake db:fix_accents</code> to clean up encoding problems in the safe2pee data. (Use <code>rake db:fix_accents[dry_run]</code> to preview the changes.)
+
+### 6 Assets
 * [Assets Repo](https://github.com/RefugeRestrooms/refuge_assets)
 
 ## Testing

Rakefile

@@ -5,3 +5,6 @@ require File.expand_path('../config/application', __FILE__)
 
 SaferstallsRails::Application.load_tasks
 
+Dir.glob('.rake/*.rb').each do |f|
+  import f
+end

Vagrantfile

@@ -0,0 +1,54 @@
+# -*- mode: ruby -*-
+# vi: set ft=ruby :
+
+# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
+VAGRANTFILE_API_VERSION = "2"
+BOXNAME = "refugerestrooms"
+
+Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
+  # Ubuntu 18.04 base box
+  config.vm.box = "ubuntu/bionic64"
+  config.vm.hostname = BOXNAME
+  #config.vm.box_download_checksum = 
+
+  # Disable automatic box update checking. If you disable this, then
+  # boxes will only be checked for updates when the user runs
+  # `vagrant box outdated`. This is not recommended.
+  # config.vm.box_check_update = false
+
+  # Access the rails server at localhost:3000
+  config.vm.network "forwarded_port", guest: 3000, host: 3000
+
+  # Use this if you need to copy files via scp or something
+  # config.vm.network "private_network", ip: "192.168.33.10"
+
+  # If true, then any SSH connections made will enable agent forwarding.
+  # Default value: false
+  # config.ssh.forward_agent = true
+
+  # View virtualbox provider docs for more options
+  config.vm.provider "virtualbox" do |vb|
+    vb.name = BOXNAME
+    # Uncomment this if you need more than default of 512
+    vb.customize ["modifyvm", :id, "--memory", "1024"]
+  end
+
+  # If this gets bigger I can make it into a chef run
+  # mi-wood
+  config.vm.provision "shell", path: "setup/setup_vagrant.sh", privileged: false
+
+  # Enable provisioning with chef solo, specifying a cookbooks path, roles
+  # path, and data_bags path (all relative to this Vagrantfile), and adding
+  # some recipes and/or roles.
+  #
+  # config.vm.provision "chef_solo" do |chef|
+  #   chef.cookbooks_path = "../my-recipes/cookbooks"
+  #   chef.roles_path = "../my-recipes/roles"
+  #   chef.data_bags_path = "../my-recipes/data_bags"
+  #   chef.add_recipe "mysql"
+  #   chef.add_role "web"
+  #
+  #   # You may also specify custom JSON attributes:
+  #   chef.json = { mysql_password: "foo" }
+  # end
+end

config/database.yml

@@ -1,17 +1,13 @@
-default: &default
+development:
   adapter: postgresql
   encoding: unicode
-  host: db
-  username: postgres
-  password:
-  pool: 5
-
-development:
-  <<: *default
   database: bathrooms_development
-
+  pool: 5
+  host: localhost
 
 test:
-  <<: *default
+  adapter: postgresql
+  encoding: unicode
   database: bathrooms_test
-
+  pool: 5
+  host: localhost

setup/pg_hba.conf

@@ -0,0 +1,99 @@
+# PostgreSQL Client Authentication Configuration File
+# ===================================================
+#
+# Refer to the "Client Authentication" section in the PostgreSQL
+# documentation for a complete description of this file.  A short
+# synopsis follows.
+#
+# This file controls: which hosts are allowed to connect, how clients
+# are authenticated, which PostgreSQL user names they can use, which
+# databases they can access.  Records take one of these forms:
+#
+# local      DATABASE  USER  METHOD  [OPTIONS]
+# host       DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
+# hostssl    DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
+# hostnossl  DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
+#
+# (The uppercase items must be replaced by actual values.)
+#
+# The first field is the connection type: "local" is a Unix-domain
+# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
+# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
+# plain TCP/IP socket.
+#
+# DATABASE can be "all", "sameuser", "samerole", "replication", a
+# database name, or a comma-separated list thereof. The "all"
+# keyword does not match "replication". Access to replication
+# must be enabled in a separate record (see example below).
+#
+# USER can be "all", a user name, a group name prefixed with "+", or a
+# comma-separated list thereof.  In both the DATABASE and USER fields
+# you can also write a file name prefixed with "@" to include names
+# from a separate file.
+#
+# ADDRESS specifies the set of hosts the record matches.  It can be a
+# host name, or it is made up of an IP address and a CIDR mask that is
+# an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
+# specifies the number of significant bits in the mask.  A host name
+# that starts with a dot (.) matches a suffix of the actual host name.
+# Alternatively, you can write an IP address and netmask in separate
+# columns to specify the set of hosts.  Instead of a CIDR-address, you
+# can write "samehost" to match any of the server's own IP addresses,
+# or "samenet" to match any address in any subnet that the server is
+# directly connected to.
+#
+# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
+# "krb5", "ident", "peer", "pam", "ldap", "radius" or "cert".  Note that
+# "password" sends passwords in clear text; "md5" is preferred since
+# it sends encrypted passwords.
+#
+# OPTIONS are a set of options for the authentication in the format
+# NAME=VALUE.  The available options depend on the different
+# authentication methods -- refer to the "Client Authentication"
+# section in the documentation for a list of which options are
+# available for which authentication methods.
+#
+# Database and user names containing spaces, commas, quotes and other
+# special characters must be quoted.  Quoting one of the keywords
+# "all", "sameuser", "samerole" or "replication" makes the name lose
+# its special character, and just match a database or username with
+# that name.
+#
+# This file is read on server startup and when the postmaster receives
+# a SIGHUP signal.  If you edit the file on a running system, you have
+# to SIGHUP the postmaster for the changes to take effect.  You can
+# use "pg_ctl reload" to do that.
+
+# Put your actual configuration here
+# ----------------------------------
+#
+# If you want to allow non-local connections, you need to add more
+# "host" records.  In that case you will also need to make PostgreSQL
+# listen on a non-local interface via the listen_addresses
+# configuration parameter, or via the -i or -h command line switches.
+
+
+
+
+# DO NOT DISABLE!
+# If you change this first entry you will need to make sure that the
+# database superuser can access the database using some other method.
+# Noninteractive access to all databases is required during automatic
+# maintenance (custom daily cronjobs, replication, and similar tasks).
+#
+# Database administrative login by Unix domain socket
+local   all             postgres                                peer
+
+# TYPE  DATABASE        USER            ADDRESS                 METHOD
+
+# "local" is for Unix domain socket connections only
+local   all             all                                     trust
+# IPv4 local connections:
+host    all             all             127.0.0.1/32            trust
+# IPv6 local connections:
+host    all             all             ::1/128                 trust
+# Allow replication connections from localhost, by a user with the
+# replication privilege.
+#local   replication     postgres                                peer
+#host    replication     postgres        127.0.0.1/32            md5
+#host    replication     postgres        ::1/128                 md5