bundlegem 0.0.9 → 0.0.10
Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: b3f872d489dd650a28de1c63a08811d517730bd4
|
|
4
|
+
data.tar.gz: 122dbfd04fdeb5daf3760c04616543a334467be8
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 32d6e0755a9ff109194f776ffedfa355c9490f3c2b4e54b9d1482ce43c971ebddaaa1c336ea05ee1b8e38c86bc6f63c60a068a3b00e5b9c86359a636493b50ba
|
|
7
|
+
data.tar.gz: cd202e82a1c0f846f8aa18997770c71a0076f8ad37e960473282f55ddbc1fc7ebb428846a256e1a06559d47533ad2b4a1756206337f221633f6caa011be94468
|
data/README.md
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
# BundleGem: A Gem Project Generator with User Defined Templates
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Alot of the code here was extracted from Bundler's `bundle gem` command, so credits to Bundler folks. Originally I planned to make the new features accessible to the Bundler team and so tried to keep the code as similar to their project as possible, but ultimately discovered that they don't want to feature to grow because good tools should do a single thing very well (manage dependencies), not many things (manage dependencies and also do random other helpful stuff).
|
|
4
4
|
|
|
5
5
|
The goal of the project is to allow users to define templates in the most native form to all technologist: Directory Structures, short commands, and helpful commands which make the gem's usage completely visible!
|
|
6
6
|
|
|
7
|
-
The benefits of using this repo to create gems rather than bundler is that you can choose to create 'classes' of gems. By classes, I mean that there are different typs of 'gems', there are basic library gems, that are just code and can only be used from other code, there are command line application gems, those are gems that are run on the command line and include a binary file, and there are also web interface gems, those are gems which spin up a simple web interface and request that the user connect to it's server on what ever port it has spun up on. Depending on your field of specialty, you may be able to imagine other classes of gems that will aid you in your work.
|
|
7
|
+
The benefits of using this repo to create gems rather than bundler is that you can choose to create 'classes' of gems. By classes, I mean that there are different typs of 'gems', there are basic library gems, that are just code and can only be used from other code, there are command line application gems, those are gems that are run on the command line and include a binary file, and there are also web interface gems, those are gems which spin up a simple web interface and request that the user connect to it's server on what ever port it has spun up on. Depending on your field of specialty, you may be able to imagine other classes of gems that will aid you in your work.
|
|
8
8
|
|
|
9
|
-
All of these 'classes of gems' as I refer to them, start out with a different code base, consistent with all other gems of the same class. This 'class based' aproach to gem creation is different from the addative approach that other gem genorators are based on.
|
|
9
|
+
All of these 'classes of gems' as I refer to them, start out with a different code base, consistent with all other gems of the same class. This 'class based' aproach to gem creation is different from the addative approach that other gem genorators are based on.
|
|
10
10
|
|
|
11
|
-
The most benificial aspect of this gem is that it allows users to specify exactly how they want their 'default starting gem' to look like, rather than rely on what someone else thought their default starting gem should look like.
|
|
11
|
+
The most benificial aspect of this gem is that it allows users to specify exactly how they want their 'default starting gem' to look like, rather than rely on what someone else thought their default starting gem should look like.
|
|
12
12
|
|
|
13
13
|
### Installation and usage
|
|
14
14
|
|
|
@@ -21,8 +21,8 @@ Then create a new template for a gem class you expect to use more than once:
|
|
|
21
21
|
```
|
|
22
22
|
$ bundlegem --newtemplate
|
|
23
23
|
Specify a name for your gem template: my_service
|
|
24
|
-
Specify description:
|
|
25
|
-
Specify template tag name [MISC]:
|
|
24
|
+
Specify description:
|
|
25
|
+
Specify template tag name [MISC]:
|
|
26
26
|
Cloning base project structure into ~/.bundlegem/templates/my_service
|
|
27
27
|
...
|
|
28
28
|
Complete!
|
|
@@ -43,7 +43,7 @@ EMBEDDED:
|
|
|
43
43
|
|
|
44
44
|
```
|
|
45
45
|
|
|
46
|
-
You'll now find a project skeleton in ~/.bundlegem/templates/my_service that you can customize to your liking.
|
|
46
|
+
You'll now find a project skeleton in ~/.bundlegem/templates/my_service that you can customize to your liking.
|
|
47
47
|
|
|
48
48
|
|
|
49
49
|
Finally, create a new gem using your new gem template:
|
|
@@ -66,5 +66,5 @@ You'll get a good idea as to the possibilities by inspecting the files in [templ
|
|
|
66
66
|
|
|
67
67
|
### Contributing
|
|
68
68
|
|
|
69
|
-
Please feel free to speak up using the issue section if there's anything on your mind :)
|
|
70
|
-
Do the usual fork routine and issue a pull request by all means.
|
|
69
|
+
Please feel free to speak up using the issue section if there's anything on your mind :)
|
|
70
|
+
Do the usual fork routine and issue a pull request by all means.
|
data/lib/bundlegem/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: bundlegem
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.0.
|
|
4
|
+
version: 0.0.10
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- TheNotary
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2017-
|
|
11
|
+
date: 2017-05-28 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: thor
|