orats 5.0.1 → 5.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 36e79bf0f322b9defaa743ca95c88b59a0120dd4
-  data.tar.gz: 349f8ff57deec2802ffe5cf6da5bd6cae66b07df
+  metadata.gz: 0d7e5aa5200d6a82f91f806a1b51e71686d0b2fd
+  data.tar.gz: 97bcc8ad2a1d4ec87a6e70766fb4235f64105b95
 SHA512:
-  metadata.gz: bb3a8da069e08566e189ac967b4390d7aea9f3760fe5a8955d9c885172e2111430c98c5edba1a5b1e07cc4d1b92e82883e83516e44c24c48c6f2f369b6552406
-  data.tar.gz: b0af3616b3319ed14e499b8e4d6cfa015a8747cdd876513b1505c4917a8ae9aa1389103ee52036b05f6ed28b09e4a7a3830551a6398c4ebcddbc5869ff826b4c
+  metadata.gz: 2ea921eeeaee98d57d92f785539b9da667dda72a31637b2c7a670785c55a25c6b53b7b4fa8cff2fa075aa334b51290f909a4f082e9838083c7bdb1ed986b796b
+  data.tar.gz: e2c5a730adaa3e5cba7d8e65f4f86e5d7828f555392c7058400830a23436434cea20149617faa7c3a985c632761cfc56f0cdb75b225ce609a6c4f92c749b14ef

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+## orats 5.0.2 (July 11, 2016)
+
+- Fix `Dockerfile` to use orats_base not my_dockerized_app
+
 ## orats 5.0.1 (July 10, 2016)
 
 - Fix missing `.env` file (Fixes #12)

data/lib/orats/templates/base/Dockerfile

@@ -24,8 +24,8 @@ RUN apt-get update && apt-get install -qq -y --no-install-recommends \
 # packages to ensure that we can compile assets (nodejs) and
 # communicate with PostgreSQL (libpq-dev).
 
-ENV INSTALL_PATH /my_dockerized_app
-# The name of the application is my_dockerized_app and while there
+ENV INSTALL_PATH /orats_base
+# The name of the application is orats_base and while there
 # is no standard on where your project should live inside of the Docker
 # image, I like to put it in the root of the image and name it
 # after the project.
@@ -42,8 +42,8 @@ RUN mkdir -p $INSTALL_PATH
 
 WORKDIR $INSTALL_PATH
 # We're going to be executing a number of commands below, and
-# having to CD into the /my_dockerized_app folder every time would be
-# lame, so instead we can set the WORKDIR to be /my_dockerized_app.
+# having to CD into the /orats_base folder every time would be
+# lame, so instead we can set the WORKDIR to be /orats_base.
 #
 # By doing this, Docker will be smart enough to execute all
 # future commands from within this directory.
@@ -51,9 +51,9 @@ WORKDIR $INSTALL_PATH
 COPY Gemfile Gemfile.lock ./
 # This is going to copy in the Gemfile and Gemfile.lock from our
 # work station at a path relative to the Dockerfile to the
-# my_dockerized_app/ path inside of the Docker image.
+# orats_base/ path inside of the Docker image.
 #
-# It copies it to /my_dockerized_app because of the WORKDIR being set.
+# It copies it to /orats_base because of the WORKDIR being set.
 #
 # We copy in our Gemfile before the main app because Docker is
 # smart enough to cache "layers" when you build a Docker image.
@@ -75,7 +75,7 @@ RUN bundle install --binstubs
 COPY . .
 # This might look a bit alien but it's copying in everything from
 # the current directory relative to the Dockerfile, over to the
-# /my_dockerized_app folder inside of the Docker image.
+# /orats_base folder inside of the Docker image.
 #
 # We can get away with using the . for the second argument because
 # this is how the unix command cp (copy) works. It stands for the

data/lib/orats/version.rb

@@ -1,4 +1,4 @@
 # set the version of this gem
 module Orats
-  VERSION = '5.0.1'.freeze
+  VERSION = '5.0.2'.freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: orats
 version: !ruby/object:Gem::Version
-  version: 5.0.1
+  version: 5.0.2
 platform: ruby
 authors:
 - Nick Janetakis
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-07-10 00:00:00.000000000 Z
+date: 2016-07-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor