capistrano-container 0.0.2 → 0.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1b651e108dd83aaa200aad9f5576445e75cfeccb
-  data.tar.gz: 2a036295642ac2ea8a09fbe82549d394fa4c28e3
+  metadata.gz: 3646c958ec3169da5b3f0cd4916e05cfe0db6cec
+  data.tar.gz: 35a7965e274971b813e1b1ec2f1109acb801e90f
 SHA512:
-  metadata.gz: e4be7aa7fc3703d844cc898ad5775d9a436dfcf061010f81de94519ac41bffdf22946413fe5a973e4f8a0e7e6f15e042fd39dae2cb0c788887728e23aa27bac2
-  data.tar.gz: 98ce9c8497aa0bfe6613da4c768cb9c8a605365c345314d52457389380e9d6fe4d8dbff195c2629e1e3c095d8d1c587750aaa1ab94f18e1b8fcf5b75b2a7cd31
+  metadata.gz: 969e4c33c68c9bae39e6ccfce824fe66b368fe8ddbab37f1f68a0fbb2730012ccfe505470f223c396cecdbc8e88cf335d1b2b6b983da06777f31ee96ca11d813
+  data.tar.gz: 7f80e35576be85a3327c7bd296336748086e76b362c3f2a7a436d8dd02008f40bf9cf1e36672f60b8b929be9ff55545971ba313f2131b05ebae83c627f85de5d

data/README.md

@@ -1,14 +1,14 @@
-# Capistrano::Container [![Gem Version](https://badge.fury.io/rb/capistrano-container.svg)](http://badge.fury.io/rb/capistrano-container)
+# Capistrano::Container [![Gem Version](https://badge.fury.io/rb/capistrano-container.svg)](https://badge.fury.io/rb/capistrano-container)
 
 Helps managing [docker]() container and files inside docker container for Capistrano 3.x.
 
-This project is in an early stage but helps me alot dealing with my container deployments and keeps my code clean. It is not only ment for docker, but at the moment there only supports docker, feel free to ditribute =)
+This project is in an early stage but helps me alot dealing with my container deployments and keeps my code clean. It is not only ment for docker, but at the moment it only supports docker, feel free to distribute =)
 
 This gem does not handle Dockerfiles or such things, for that there are enough capistrano modules available.
 
 ## Installation
 
-Add this line to your application's Gemfile:
+Add this lines to your application's Gemfile:
 
 ```ruby
 gem 'capistrano', '>= 3.0.0'
@@ -31,7 +31,7 @@ require 'capistrano/container'
 
 ## Usage
 ### definition
-To define and register a container do the following in you stage config or deploy.rb:
+To define and register a container do the following in your stage config or deploy.rb:
 
 ```ruby
 ...
@@ -51,9 +51,9 @@ container 'php', roles: %w{php},
 
 This registers two container (db, php) for the server www.example.com. The roles can later be used to filter container like the way you filter server in capistrano.
 
-The container id is optional. If not set the ontainer id is equal to the name you give the container as first argument. The container id will later be used to run docker commands.
+The container id is optional. If not set, the container id is equal to the name you give the container as first argument. The container id will later be used to run docker commands.
 
-If you define a container, the given hosts get the role `:container_host` behind the scenes, so you can filter hosts that running container. Also a container specific role will be added, fo container named php `:container_php`.
+If you define a container, the role `:container_host` will be added to the given hosts, so you can filter hosts that are running container. Also a container specific role will be added, for a container named php `:container_php`.
 
 
 ### commandline tasks
@@ -77,7 +77,7 @@ cap container:unpause              # unpause a docker container
 cap container:update_docker        # update docker
 ```
 
-For every registered container also specific tasks will be registered. For a container named php the following tasks will be available. (With `cap -T` you will the container specific tasks only see if you register your container in the deploy.rb)
+For every registered container, individual tasks will be creazed. For a container named php the following tasks will be available. (With `cap -T` you can see the container specific tasks, but only if you register your container in the deploy.rb and not in the stage file)
 
 ```ruby
 cap container:php:delete           # delete a docker container
@@ -108,7 +108,7 @@ after :deploy, :updated do
   end
 end
 ```
-This filter container with the role `:php` and invokes the task `container:#{container.name}:restart`.
+This filters container with the role `:php` and invokes the task `container:#{container.name}:restart`.
 
 Or inside other tasks
 ```ruby
@@ -117,7 +117,9 @@ Or inside other tasks
   container = container_by_id 'website_company_beta_db'
 ```
 
-A container instance has the following methods:
+Note that you have to use this commands inside a SSHKit context, means inside a `on roles :containers_host do` block for example.
+
+A container has the following methods:
 ```ruby
   # tests if the container has a specific role
   def has_role?(role)
@@ -142,10 +144,14 @@ A container instance has the following methods:
 ```
 
 ## TODO
-  * Implement provider pattern for other container manager.
   * Write tests.
+  * Implement provider pattern for other container manager.
 
 ## Changes
+### Version 0.0.3
+  * use sh instead of bash for docker exec
+  * use correct github url
+
 ### Version 0.0.2
   * Initial release
 

data/capistrano-container.gemspec

@@ -4,14 +4,14 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 
 Gem::Specification.new do |spec|
   spec.name        = 'capistrano-container'
-  spec.version     = '0.0.2'
-  spec.date        = '2016-06-08'
+  spec.version     = '0.0.3'
+  spec.date        = '2016-09-26'
   spec.summary     = 'Helps managing docker container and files inside docker container for Capistrano 3.x'
   spec.description = spec.summary
   spec.authors     = ['Tom Hanoldt']
   spec.email       = ['tom@creative-workflow.berlin']
   spec.files       = ['lib/hola.rb']
-  spec.homepage    = 'https://gihub.com/creative-workflow/capistrano-container'
+  spec.homepage    = 'https://github.com/creative-workflow/capistrano-container'
   spec.license     = 'MIT'
 
   spec.files         = `git ls-files`.split($/)

data/lib/capistrano/container/instance.rb

@@ -50,7 +50,7 @@ class Instance
   end
 
   def execute(command)
-    command = "docker exec -i #{container_id} bash -c '#{command.gsub("'", "\'")}'"
+    command = "docker exec -i #{container_id} sh -c '#{command.gsub("'", "\'")}'"
 
     @dsl.execute(command)
   end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: capistrano-container
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
 platform: ruby
 authors:
 - Tom Hanoldt
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-06-08 00:00:00.000000000 Z
+date: 2016-09-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: capistrano
@@ -64,7 +64,6 @@ files:
 - Gemfile
 - LICENSE
 - README.md
-- README0.md
 - Rakefile
 - capistrano-container.gemspec
 - lib/capistrano-container.rb
@@ -73,7 +72,7 @@ files:
 - lib/capistrano/container/manager.rb
 - lib/capistrano/container/mixins.rb
 - lib/capistrano/tasks/container.rb
-homepage: https://gihub.com/creative-workflow/capistrano-container
+homepage: https://github.com/creative-workflow/capistrano-container
 licenses:
 - MIT
 metadata: {}
@@ -93,7 +92,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.6
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: Helps managing docker container and files inside docker container for Capistrano

data/README0.md

@@ -1,74 +0,0 @@
-# Capistrano::pm2 [![Gem Version](https://badge.fury.io/rb/capistrano-pm2.svg)](http://badge.fury.io/rb/capistrano-pm2)
-
-nodejs [pm2](https://github.com/Unitech/pm2) support for Capistrano 3.x
-
-## Installation
-
-Add this line to your application's Gemfile:
-
-```ruby
-gem 'capistrano', '~> 3.1.0'
-gem 'capistrano-pm2'
-```
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install capistrano-pm2
-
-## Usage
-
-Require in `Capfile` to use the default task:
-
-```ruby
-require 'capistrano/pm2'
-```
-
-The task will run before `deploy:restart` as part of Capistrano's default deploy,
-or can be run in isolation with `cap production pm2:restart`. You can also invoke it in your `deploy.rb`:
-```ruby
-namespace :deploy do
-  desc 'Restart application'
-  task :restart do
-    # invoke 'npm:install'
-    invoke 'pm2:restart'
-  end
-
-  after :publishing, :restart
-end
-```
-
-
-Available Tasks
-```ruby
-cap pm2:delete                     # Delete pm2 application
-cap pm2:list                       # Show pm2 application info
-cap pm2:logs                       # Watch pm2 logs
-cap pm2:restart                    # Restart app gracefully
-cap pm2:setup                      # Install pm2 via npm on the remote host
-cap pm2:start                      # Start pm2 application
-cap pm2:status                     # List all pm2 applications
-cap pm2:stop                       # Stop pm2 application
-cap pm2:save                       # Save pm2 state so it can be loaded after restart
-```
-
-Configurable options:
-```ruby
-set :pm2_app_command, 'main.js'                   # default, runs main.js
-set :pm2_app_name, nil                            # app name for pm2, default cap :application
-set :pm2_target_path, -> { release_path.join('subdir') } # default not set
-set :pm2_roles, :all                              # default, cap roles to run on
-set :pm2_env_variables, {}                        # default, env vars for pm2
-set :pm2_start_params, ''                         # default, pm2 start params see http://pm2.keymetrics.io/docs/usage/quick-start/#cheat-sheet
-```
-
-## Contributing
-
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request