vagrant-registration 1.3.1 → 1.3.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +5 -5
- data/Gemfile +1 -1
- data/README.adoc +27 -4
- data/lib/vagrant-registration/version.rb +1 -1
- metadata +3 -5
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
|
-
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: 7e6fbd467ace0a36ad6a8ed998000cd0c636519b320664c7ab33d5bc2c6fc9bc
|
4
|
+
data.tar.gz: 86eb123fdd8e92205ee2e39e265b4cae3b0db1ad9d655ed18d2e606d075d3c01
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 88295a8a884ba2d1da7b1912b9900d01328557f77b12ae1970d7fe12c06a3f34d7e0499c29d83b4ba1fd6b29472225378bbd8079fee6a8447ad24b9b15d7191e
|
7
|
+
data.tar.gz: 1014dd664621d43ea0d8c95aaaeddfa6066eb219bae4f47b8d5f0b23fc3c4c93755b2c21118c714f1e4b22bc15c87b1c42af2f4ab36aff61ab6411584ad72a2a
|
data/Gemfile
CHANGED
data/README.adoc
CHANGED
@@ -398,17 +398,22 @@ option to `false`:
|
|
398
398
|
|
399
399
|
== Development
|
400
400
|
|
401
|
+
The use of https://rvm.io[RVM] is recommended. Verified to work with
|
402
|
+
ruby 2.0.0p648.
|
403
|
+
|
404
|
+
....
|
405
|
+
rvm install 2.0
|
406
|
+
rvm use 2.0
|
407
|
+
....
|
408
|
+
|
401
409
|
To install a development environment, clone the repo and prepare
|
402
410
|
dependencies by:
|
403
411
|
|
404
412
|
....
|
405
413
|
gem install bundler
|
406
|
-
|
414
|
+
bundle install
|
407
415
|
....
|
408
416
|
|
409
|
-
The use of https://rvm.io[RVM] is recommended. Verified to work with
|
410
|
-
ruby 2.0.0p643.
|
411
|
-
|
412
417
|
=== Tests
|
413
418
|
|
414
419
|
==== Minitest
|
@@ -460,6 +465,24 @@ __build/features_report.html__. They can also be opened via:
|
|
460
465
|
$ bundle exec rake features:open_report
|
461
466
|
....
|
462
467
|
|
468
|
+
== Releasing
|
469
|
+
|
470
|
+
To release a new version of vagrant-registration you will need to do the following:
|
471
|
+
|
472
|
+
*(only contributors of the GitHub repo and owners of the project at RubyGems will have rights to do this)*
|
473
|
+
|
474
|
+
1. First, bump, commit, and push the version in ~/lib/vagrant-registration/version.rb:
|
475
|
+
* Follow [Semantic Versioning](http://semver.org/).
|
476
|
+
2. Then, create a matching GitHub Release (this will also create a tag):
|
477
|
+
* Preface the version number with a `v`.
|
478
|
+
* https://github.com/devopsgroup-io/vagrant-hostmanager/releases
|
479
|
+
3. You will then need to build and push the new gem to RubyGems:
|
480
|
+
* `rake gem:build`
|
481
|
+
* `gem push pkg/vagrant-registration-1.6.1.gem`
|
482
|
+
4. Then, when John Doe runs the following, they will receive the updated vagrant-registration plugin:
|
483
|
+
* `vagrant plugin update`
|
484
|
+
* `vagrant plugin update vagrant-registration`
|
485
|
+
|
463
486
|
== Acknowledgements
|
464
487
|
|
465
488
|
The project would like to make sure we thank
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: vagrant-registration
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.3.
|
4
|
+
version: 1.3.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Langdon White
|
@@ -10,7 +10,7 @@ authors:
|
|
10
10
|
autorequire:
|
11
11
|
bindir: bin
|
12
12
|
cert_chain: []
|
13
|
-
date:
|
13
|
+
date: 2019-12-17 00:00:00.000000000 Z
|
14
14
|
dependencies: []
|
15
15
|
description: Enables guests to be registered automatically which is especially useful
|
16
16
|
for RHEL or SLES guests.
|
@@ -60,10 +60,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
60
60
|
- !ruby/object:Gem::Version
|
61
61
|
version: 1.3.6
|
62
62
|
requirements: []
|
63
|
-
|
64
|
-
rubygems_version: 2.4.8
|
63
|
+
rubygems_version: 3.0.4
|
65
64
|
signing_key:
|
66
65
|
specification_version: 4
|
67
66
|
summary: Automatic guest registration for Vagrant
|
68
67
|
test_files: []
|
69
|
-
has_rdoc:
|