yaml-exec 0.1.0 → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (6) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +19 -4
  3. data/lib/yaml/exec/version.rb +1 -1
  4. metadata +1 -3
  5. data/bin/console +0 -14
  6. data/bin/setup +0 -7
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 2d0b0dd8ffa5d8ee8728ae465b9e1d00613d2a40
4
- data.tar.gz: b9911abf6fd442c752aafe423215944ba4cb90a0
3
+ metadata.gz: 0bd2709170a44afdec49a433002cd0519121752e
4
+ data.tar.gz: fe5506e5e0541f054ffe2fe9f82da4c4af44d905
5
5
  SHA512:
6
- metadata.gz: 72881bc4d462bc24095f245b2e3973cbb4feeda133f62d87707d3f6962a5347f8391c097c69a77f560b6a8f65e960e33a827db9fc218568d79ad29bbf26a43bc
7
- data.tar.gz: d7d13369a5b01af807ce48305c94d9555f249448fed56f14c7eacf69be4a6fb04eb4b8e9c2601e2fc4258f3a4f65d5afe9ff17f60c58b8a26244d14a5653ddc0
6
+ metadata.gz: 5a3655402a269e47d35a5aa6f8cf20f60159a0f37b1b3c05dfc7be12324b176cde50cdf4b5f1a07f0e7031c2f506601ef88323c90bb66b6f740e27d96d506942
7
+ data.tar.gz: 3454f831910e2e10524393b304fc437ebc43dceb23d20b43286a71c2cf5aacbb76a9ba42960aa6215a51b8530a0f6eaa349b7b7383185a08592eec855b4b8340
data/README.md CHANGED
@@ -1,8 +1,6 @@
1
1
  # Yaml::Exec
2
2
 
3
- Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/yaml/exec`. To experiment with that code, run `bin/console` for an interactive prompt.
4
-
5
- TODO: Delete this and the text above, and describe your gem
3
+ Execute command with complicated arguments in a YAML file.
6
4
 
7
5
  ## Installation
8
6
 
@@ -22,7 +20,24 @@ Or install it yourself as:
22
20
 
23
21
  ## Usage
24
22
 
25
- TODO: Write usage instructions here
23
+ $ yaml-exec <command> <yaml file>
24
+
25
+ ## Example
26
+
27
+ $ yaml-exec docker-machine create machines.yml
28
+
29
+ machines.yml:
30
+
31
+ web:
32
+ driver: virtualbox
33
+ engine-env:
34
+ HTTP_PROXY: http://example.com:8080
35
+ HTTPS_PROXY: https://example.com:8080
36
+ NO_PROXY: example2.com
37
+
38
+ The output
39
+
40
+ docker-machine create --driver virtualbox --engine-env HTTP_PROXY=http://example.com:8080 --engine-env HTTPS_PROXY=https://example.com:8080 --engine-env NO_PROXY=example2.com web
26
41
 
27
42
  ## Development
28
43
 
data/lib/yaml/exec/version.rb CHANGED
@@ -1,5 +1,5 @@
1
1
  module Yaml
2
2
  module Exec
3
- VERSION = "0.1.0"
3
+ VERSION = "0.1.1"
4
4
  end
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: yaml-exec
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.0
4
+ version: 0.1.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Genki Takiuchi
@@ -54,8 +54,6 @@ files:
54
54
  - LICENSE.txt
55
55
  - README.md
56
56
  - Rakefile
57
- - bin/console
58
- - bin/setup
59
57
  - exe/yaml-exec
60
58
  - lib/yaml/exec.rb
61
59
  - lib/yaml/exec/version.rb
data/bin/console DELETED
@@ -1,14 +0,0 @@
1
- #!/usr/bin/env ruby
2
-
3
- require "bundler/setup"
4
- require "yaml/exec"
5
-
6
- # You can add fixtures and/or initialization code here to make experimenting
7
- # with your gem easier. You can also use a different console, if you like.
8
-
9
- # (If you use this, don't forget to add pry to your Gemfile!)
10
- # require "pry"
11
- # Pry.start
12
-
13
- require "irb"
14
- IRB.start
data/bin/setup DELETED
@@ -1,7 +0,0 @@
1
- #!/bin/bash
2
- set -euo pipefail
3
- IFS=$'\n\t'
4
-
5
- bundle install
6
-
7
- # Do any other automated setup that you need to do here