trustygems 0.1.0 → 0.2.0
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 -1
- data/README.md +48 -0
- data/lib/trustygems/version.rb +1 -1
- data/lib/trustygems.rb +1 -1
- metadata +4 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 20b82932774e70c1ed20be3d583e0259f6105b00
|
4
|
+
data.tar.gz: 5bbe4044135c17e04eef67abb5e84f1ba313e2ce
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: aa5ded7cdf867cc614b2c8bc0d21a70b6a068767beb2069e72eadd9fcbc49bd81a50d79a2dc4a66dd21d1cb5a003f8dad31630d361643a8857299533c9d3a2ce
|
7
|
+
data.tar.gz: 3ace038c7f491baea64aedd0c32295e58e82d8c91ad6b39bdf82d9b9a83c46f4afb36f5b777d59b644c011f8eeab8563cddc6ec503647451ac99bbd966ebf76b
|
data/Gemfile.lock
CHANGED
data/README.md
ADDED
@@ -0,0 +1,48 @@
|
|
1
|
+
#Trustygems
|
2
|
+
|
3
|
+
##What is Trustygems?
|
4
|
+
|
5
|
+
Trustygems is a simple rake task wrapper around the gem build and push process. It allows a project to include a simple yml file that tells Trustygems what gemspec to build, and what command to use to push it to a repository.
|
6
|
+
|
7
|
+
This is useful if you have some public gems on Rubygems and other gems stored on a private gem server, like geminabox. Instead of needing to remember which repository hosts each project, you can simply configure it once, run the trusygems deploy command, and let the gem do the work.
|
8
|
+
|
9
|
+
##Installation
|
10
|
+
|
11
|
+
To install Trustygems, simply include it in your Gemfile like this:
|
12
|
+
|
13
|
+
```ruby
|
14
|
+
gem 'trustygems', '~> 0.1.0'
|
15
|
+
```
|
16
|
+
|
17
|
+
Then create a **trustygems.yml** in the project's config directory. Only two things need defined. The config file for this project, for instance, is this:
|
18
|
+
|
19
|
+
```YAML
|
20
|
+
gemspec: trustygems.gemspec
|
21
|
+
deploy_command: gem push
|
22
|
+
```
|
23
|
+
|
24
|
+
For your project, you'll just need to replace the gemspec attribute with the name of your project's gemspec file. Also, if you're not pushing to rubygems, you'll need to replace the deploy_command attribute. For instance, if using geminabox, you'd change it to **gem inabox**.
|
25
|
+
|
26
|
+
Finally, within your project's Rakefile, include the following line to load Trustygems' rake task:
|
27
|
+
|
28
|
+
```ruby
|
29
|
+
require 'trustygems'
|
30
|
+
```
|
31
|
+
|
32
|
+
##Deploying With Trustygems
|
33
|
+
|
34
|
+
Once you're ready to push a new version of one of your gems, run the Trustygems rake deploy command:
|
35
|
+
|
36
|
+
```
|
37
|
+
rake trustygems:deploy
|
38
|
+
```
|
39
|
+
|
40
|
+
This will build your gem, then push it to Rubygems (or wherever your private server is).
|
41
|
+
|
42
|
+
And that's it!
|
43
|
+
|
44
|
+
|
45
|
+
|
46
|
+
|
47
|
+
|
48
|
+
|
data/lib/trustygems/version.rb
CHANGED
data/lib/trustygems.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: trustygems
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.2.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Eric Sipple
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2015-
|
11
|
+
date: 2015-08-10 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: rake
|
@@ -35,6 +35,7 @@ files:
|
|
35
35
|
- GEMFILE
|
36
36
|
- Gemfile.lock
|
37
37
|
- LICENSE
|
38
|
+
- README.md
|
38
39
|
- Rakefile
|
39
40
|
- config/trustygems.yml
|
40
41
|
- lib/generators/templates/trustygems.yml.erb
|
@@ -62,7 +63,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
62
63
|
version: '0'
|
63
64
|
requirements: []
|
64
65
|
rubyforge_project:
|
65
|
-
rubygems_version: 2.4.
|
66
|
+
rubygems_version: 2.4.6
|
66
67
|
signing_key:
|
67
68
|
specification_version: 4
|
68
69
|
summary: Standaridizing gem deploy commands, regardless of destination.
|