directory_template 1.0.0 → 1.0.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.
- data/directory_template.gemspec +16 -7
- data/lib/directory_template.rb +1 -1
- data/lib/directory_template/version.rb +1 -1
- metadata +30 -8
data/directory_template.gemspec
CHANGED
@@ -2,18 +2,27 @@
|
|
2
2
|
|
3
3
|
Gem::Specification.new do |s|
|
4
4
|
s.name = "directory_template"
|
5
|
-
s.version = "1.0.
|
5
|
+
s.version = "1.0.1"
|
6
6
|
s.authors = "Stefan Rusterholz"
|
7
7
|
s.homepage = "https://github.com/apeiros/directory_template"
|
8
8
|
s.description = <<-DESCRIPTION.gsub(/^ /, '').chomp
|
9
|
-
|
10
|
-
|
11
|
-
|
12
|
-
|
13
|
-
|
9
|
+
DirectoryTemplate is a library which lets you generate directory structures and files
|
10
|
+
from a template structure. The template structure can be a real directory structure on
|
11
|
+
the filesystem, or it can be stored in a yaml file. Take a look at the examples directory
|
12
|
+
in the gem to get an idea, how a template can look.
|
13
|
+
|
14
|
+
When generating a new directory structure from a template, DirectoryTemplate will process
|
15
|
+
the pathname of each directory and file using the DirectoryTemplate#path_processor.
|
16
|
+
It will also process the contents of each file with all processors that apply to a given
|
17
|
+
file.
|
18
|
+
The standard path processor allows you to use `%{variables}` in pathnames. The gem comes
|
19
|
+
with a .erb (renders ERB templates) and .html.markdown processor (renders markdown to
|
20
|
+
html).
|
21
|
+
You can use the existing processors or define your own ones.
|
14
22
|
DESCRIPTION
|
15
23
|
s.summary = <<-SUMMARY.gsub(/^ /, '').chomp
|
16
|
-
|
24
|
+
Lets you generate directory structures from a template, optionally processing paths
|
25
|
+
(variables in the path) and contents (e.g., render ERB templates).
|
17
26
|
SUMMARY
|
18
27
|
s.email = "stefan.rusterholz@gmail.com"
|
19
28
|
|
data/lib/directory_template.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: directory_template
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.0.
|
4
|
+
version: 1.0.1
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -11,16 +11,37 @@ bindir: bin
|
|
11
11
|
cert_chain: []
|
12
12
|
date: 2012-05-03 00:00:00.000000000 Z
|
13
13
|
dependencies: []
|
14
|
-
description: ! '
|
14
|
+
description: ! 'DirectoryTemplate is a library which lets you generate directory structures
|
15
|
+
and files
|
15
16
|
|
16
|
-
|
17
|
-
|
17
|
+
from a template structure. The template structure can be a real directory structure
|
18
|
+
on
|
18
19
|
|
19
|
-
|
20
|
+
the filesystem, or it can be stored in a yaml file. Take a look at the examples
|
21
|
+
directory
|
20
22
|
|
21
|
-
|
23
|
+
in the gem to get an idea, how a template can look.
|
22
24
|
|
23
|
-
|
25
|
+
|
26
|
+
When generating a new directory structure from a template, DirectoryTemplate will
|
27
|
+
process
|
28
|
+
|
29
|
+
the pathname of each directory and file using the DirectoryTemplate#path_processor.
|
30
|
+
|
31
|
+
It will also process the contents of each file with all processors that apply to
|
32
|
+
a given
|
33
|
+
|
34
|
+
file.
|
35
|
+
|
36
|
+
The standard path processor allows you to use `%{variables}` in pathnames. The gem
|
37
|
+
comes
|
38
|
+
|
39
|
+
with a .erb (renders ERB templates) and .html.markdown processor (renders markdown
|
40
|
+
to
|
41
|
+
|
42
|
+
html).
|
43
|
+
|
44
|
+
You can use the existing processors or define your own ones.'
|
24
45
|
email: stefan.rusterholz@gmail.com
|
25
46
|
executables: []
|
26
47
|
extensions: []
|
@@ -71,6 +92,7 @@ rubyforge_project:
|
|
71
92
|
rubygems_version: 1.8.24
|
72
93
|
signing_key:
|
73
94
|
specification_version: 3
|
74
|
-
summary:
|
95
|
+
summary: Lets you generate directory structures from a template, optionally processing
|
96
|
+
paths (variables in the path) and contents (e.g., render ERB templates).
|
75
97
|
test_files: []
|
76
98
|
has_rdoc:
|