barnacle 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0c8dbe0e035531f309a0b26e950d85a2d4862732
-  data.tar.gz: 4c25e3cb78e1a8448b7ea4d9bccdc118c2eca1be
+  metadata.gz: a4b9824a11e061402acdd28899c4ef473dfb45b1
+  data.tar.gz: d2cbfaca9f71f56f85b0e65df2695f2c1d76bbdb
 SHA512:
-  metadata.gz: cc6589d60772aade2b54dd631473be42693a2f37297b69f6e16485c421e898418f0742e6ac07654e767e1ffc3495c063bc9beb2ef3a74719b54802de031e39e2
-  data.tar.gz: 28fe6c9065bf0db1087fcb7bbd49834f4dd895641a4a6cd8cd41068c42c59ec897a724fb2b4692b042ebf9ec07c087a3e31616fc92ac98e77ea132676b55f873
+  metadata.gz: 14e009c2729af86440bc41eb47f9101f8e06e9f38d6dc701e5e85d0044a9a945ab954622ca511469ba3ef1fc6bdecd6f25ebf18f92e7c0befc7f09bfcfbb4305
+  data.tar.gz: c5fe7113888300c72ce6facb188783ebaa9175f1ac039c71f79715c5b15bbe7a322fccd27c4ed5f48999cdb71d266729f716a6f99c7ad173ad32c009ee3260f7

data/README.md

@@ -82,7 +82,7 @@ docker run --detach=true --name=[name] --hostname=[hostname] [config.yml switche
 ##### barnacle down (runs)
 
 ```
-docker stop NAME
+docker stop [name]
 ```
 
 
@@ -96,7 +96,7 @@ docker ps -a
 ##### docker enter (executes)
 
 ```
-docker exec -ti NAME bash
+docker exec -ti [name] bash
 
 ```
 
@@ -141,6 +141,47 @@ assets, and tell the web server of the changes  in your Dockerfile.  (research
 into caching as much 'bundle install' as possible) 
 
 
+## Musings on the docker way vs. the barnacle way
+
+If you are working for hipsters.com with a valuation of a trillion dollars and
+are deploying one new host per second then the barnacle way is the wrong way.
+
+One reason why is that barnacle will build the entire final image at least once
+on every new server and this can take minutes. Another reason is that you might
+pass new deployments around as images to devops.
+
+If you're a graying neckbeard that privisions new hosts as often as you
+provision new underpants then the barnacle way can work.  You don't need to
+move things around as docker images.  You move deployments around as
+directories with scp, rsync or even ftp.  To you a docker image is just a build
+cache for a new container and it stays where it is.
+
+__Docker:__ is cool and innovative.
+
+__Barnacle:__ is a feeble ruby script written by some slacker who thinks docker is
+too complicated for him.
+
+__Docker:__ 'deployments' are passed around as images, probably using a docker registry.
+
+__Barnacle:__ 'deployments' are just folders with a barnacle directory containing a
+Dockerfile and an optional config.yml file.  Except for the base image for the
+original build a docker registry isn't used.
+
+__Docker:__ the docker host doesn't really see anything other than new images
+arriving for deployment.
+
+__Barnacle:__ you'll have deployment directories laying around.  They probably got
+there from by git or rsync.
+
+__Docker:__ images are built on dev or automatically at the official docker registry.
+
+__Barnacle:__ images are built on the production host, kept around just for caching
+purposes, and are otherwise given no notice.
+
+
+
+
+
 
 ## Contributing
 

data/exe/barnacle

@@ -46,13 +46,12 @@ end
 #-------------------------------------------------------------------------------
 if File.exists?(yml_filename)
   if docker_yml = YAML.load_file(yml_filename)['docker']
-    p docker_yml
     options.merge!(docker_yml) if docker_yml
   else
-    cputs "Warning: #{yml_filename} found but didn't contain 'docker' node, not using"
+    cputs "Warning: #{yml_filename} found but didn't contain 'docker' node, can't use"
   end
 else
-  cputs "Warning: no config file found, using only defaults"
+  cputs "Warning: no config file found, using only defaults, but that's ok."
 end
 
 

data/lib/barnacle/version.rb

@@ -1,3 +1,3 @@
 module Barnacle
-  VERSION = "0.1.1"
+  VERSION = "0.1.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: barnacle
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - kswope