dctl_rb 0.3.2 → 0.3.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/Gemfile.lock +4 -4
- data/README.md +12 -4
- data/dctl_rb.gemspec +3 -3
- data/lib/dctl/version.rb +1 -1
- metadata +21 -9
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 70e30556eba70e05817d785d288cbdf4e4a7f32cbdd54272c0fe3d787e30a424
|
4
|
+
data.tar.gz: 68aef5c8617b3cc24f7d2d867d4a1cb2061cb978e950593047c35c7c87503dd2
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 1869a2bbd600e0e298099928aa5f8d4c975ad978f25961b40b3bd29cfbf9d706567263bcf52635f2bf487a7ed3111a8d6c9476b5d974e2813885a4672fdbbef5
|
7
|
+
data.tar.gz: 248644a3e1e9055df4e0620fbf40eaab408cf0ed0db87b6e3c2071aafba8022db37045a75c607de9112f0d72af4458ddfd826b8c4c58dd88dd62fe7a05a26933
|
data/Gemfile.lock
CHANGED
data/README.md
CHANGED
@@ -5,7 +5,7 @@ Choosing how to organize your application's containers across multiple environme
|
|
5
5
|
By using a standardized directory structure across your apps, you can:
|
6
6
|
1. Easily onboard new developers
|
7
7
|
2. Not reinvent the wheel for every new app
|
8
|
-
3. Let other people handle the annoying parts of docker-compose for you
|
8
|
+
3. Let other people handle the annoying parts of docker-compose for you
|
9
9
|
|
10
10
|
## Usage
|
11
11
|
|
@@ -13,7 +13,8 @@ Mostly use the same way you would use `docker-compose`, but without specifying a
|
|
13
13
|
|
14
14
|
Each command relies on information in the `docker-compose.yaml` for the given environment to determine things like tag versions.
|
15
15
|
|
16
|
-
The default environment is `dev`, but you can override this with `--env prod` etc
|
16
|
+
The default environment is `dev`, but you can override this with `--env prod` etc.
|
17
|
+
* This just tells dctl where to look for your compose file--it doesn't actually do anything different. See [Installation](#Installation) for more info.
|
17
18
|
|
18
19
|
* `dctl up`
|
19
20
|
* `dctl down`
|
@@ -36,12 +37,19 @@ Most commands also allow you to specify a specific image to target (defaulting t
|
|
36
37
|
There are also some non-compose commands to make your life easier
|
37
38
|
|
38
39
|
* `dctl connect app`
|
39
|
-
* Start a new shell in a running `app` container
|
40
|
+
* Start a new shell in a running `app` container.
|
40
41
|
* `dctl attach app`
|
41
42
|
* Attach your current TTY to that of the running `app` container.
|
42
43
|
* This is useful if you've put a debugger or something similar and need to talk directly to a running container's current shell (docker-compose eats stdin/stdout/stderr so normally this isn't possible)
|
43
44
|
* `dctl bash app`
|
44
|
-
* Spin up a new `app` image and drop you in a shell
|
45
|
+
* Spin up a new `app` image and drop you in a shell.
|
46
|
+
* `dctl recreate app`
|
47
|
+
* Stops, removes, builds, creates, and starts an image.
|
48
|
+
* Useful if you've made a change to one container but don't want to restart your entire stack to have it reflected.
|
49
|
+
* Specify `--build false` (or `-b false`) if you don't want the image to be rebuilt.
|
50
|
+
* `dctl cleanup`
|
51
|
+
* Useful for policing the large numbers of built-but-unused containers which tend to accumulate when using docker.
|
52
|
+
* Removes local images without tags and which are not referenced by other images.
|
45
53
|
|
46
54
|
## Installation
|
47
55
|
|
data/dctl_rb.gemspec
CHANGED
@@ -33,7 +33,7 @@ Gem::Specification.new do |spec|
|
|
33
33
|
spec.add_development_dependency "rake", "~> 10.0"
|
34
34
|
spec.add_development_dependency "rspec", "~> 3.0"
|
35
35
|
|
36
|
-
spec.add_dependency "thor", "
|
37
|
-
spec.add_dependency "config", "
|
38
|
-
spec.add_dependency "rainbow", "
|
36
|
+
spec.add_dependency "thor", ">= 0.20.0"
|
37
|
+
spec.add_dependency "config", ">= 1", "< 2"
|
38
|
+
spec.add_dependency "rainbow", ">= 2.2", "< 3"
|
39
39
|
end
|
data/lib/dctl/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: dctl_rb
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.3.
|
4
|
+
version: 0.3.3
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Justin Toniazzo
|
@@ -56,44 +56,56 @@ dependencies:
|
|
56
56
|
name: thor
|
57
57
|
requirement: !ruby/object:Gem::Requirement
|
58
58
|
requirements:
|
59
|
-
- - "
|
59
|
+
- - ">="
|
60
60
|
- !ruby/object:Gem::Version
|
61
61
|
version: 0.20.0
|
62
62
|
type: :runtime
|
63
63
|
prerelease: false
|
64
64
|
version_requirements: !ruby/object:Gem::Requirement
|
65
65
|
requirements:
|
66
|
-
- - "
|
66
|
+
- - ">="
|
67
67
|
- !ruby/object:Gem::Version
|
68
68
|
version: 0.20.0
|
69
69
|
- !ruby/object:Gem::Dependency
|
70
70
|
name: config
|
71
71
|
requirement: !ruby/object:Gem::Requirement
|
72
72
|
requirements:
|
73
|
-
- - "
|
73
|
+
- - ">="
|
74
74
|
- !ruby/object:Gem::Version
|
75
|
-
version: '1
|
75
|
+
version: '1'
|
76
|
+
- - "<"
|
77
|
+
- !ruby/object:Gem::Version
|
78
|
+
version: '2'
|
76
79
|
type: :runtime
|
77
80
|
prerelease: false
|
78
81
|
version_requirements: !ruby/object:Gem::Requirement
|
79
82
|
requirements:
|
80
|
-
- - "
|
83
|
+
- - ">="
|
81
84
|
- !ruby/object:Gem::Version
|
82
|
-
version: '1
|
85
|
+
version: '1'
|
86
|
+
- - "<"
|
87
|
+
- !ruby/object:Gem::Version
|
88
|
+
version: '2'
|
83
89
|
- !ruby/object:Gem::Dependency
|
84
90
|
name: rainbow
|
85
91
|
requirement: !ruby/object:Gem::Requirement
|
86
92
|
requirements:
|
87
|
-
- - "
|
93
|
+
- - ">="
|
88
94
|
- !ruby/object:Gem::Version
|
89
95
|
version: '2.2'
|
96
|
+
- - "<"
|
97
|
+
- !ruby/object:Gem::Version
|
98
|
+
version: '3'
|
90
99
|
type: :runtime
|
91
100
|
prerelease: false
|
92
101
|
version_requirements: !ruby/object:Gem::Requirement
|
93
102
|
requirements:
|
94
|
-
- - "
|
103
|
+
- - ">="
|
95
104
|
- !ruby/object:Gem::Version
|
96
105
|
version: '2.2'
|
106
|
+
- - "<"
|
107
|
+
- !ruby/object:Gem::Version
|
108
|
+
version: '3'
|
97
109
|
description:
|
98
110
|
email:
|
99
111
|
- jutonz42@gmail.com
|