RTFMd 0.10301.1 → 0.10301.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (5) hide show
  1. data/README.md +32 -32
  2. data/RTFMd.gemspec +2 -1
  3. data/bin/rtfm +0 -12
  4. data/bin/rtfmd +12 -0
  5. metadata +4 -3
data/README.md CHANGED
@@ -1,9 +1,7 @@
1
- RTFMd -- fork of gollum
2
- ========================
1
+ RTFMd
2
+ =====
3
3
 
4
- ## FORK
5
-
6
- Forked from `defunkt/gollum`:
4
+ Forked from `defunkt/gollum` with:
7
5
 
8
6
  * Sinatra mountable app
9
7
  * Stylized to look like ronn HTML man pages
@@ -13,33 +11,35 @@ Forked from `defunkt/gollum`:
13
11
 
14
12
  ## DESCRIPTION
15
13
 
16
- Gollum is a simple wiki system built on top of Git that powers GitHub Wikis.
14
+ * documentation is still a very rough WIP, so trust nothing here until I can remove the Gollum bits that no longer apply.
15
+
16
+ RTFMd is a simple wiki system built on top of Git that powers GitHub Wikis.
17
17
 
18
- Gollum wikis are simply Git repositories that adhere to a specific format.
19
- Gollum pages may be written in a variety of formats and can be edited in a
18
+ RTFMd wikis are simply Git repositories that adhere to a specific format.
19
+ RTFMd pages may be written in a variety of formats and can be edited in a
20
20
  number of ways depending on your needs. You can edit your wiki locally:
21
21
 
22
22
  * With your favorite text editor or IDE (changes will be visible after committing).
23
- * With the Gollum Ruby API.
23
+ * With the RTFMd Ruby API.
24
24
 
25
- Gollum follows the rules of [Semantic Versioning](http://semver.org/) and uses
25
+ RTFMd follows the rules of [Semantic Versioning](http://semver.org/) and uses
26
26
  [TomDoc](http://tomdoc.org/) for inline documentation.
27
27
 
28
28
 
29
29
  ## RUNNING
30
30
 
31
- To view your Gollum repository locally via the built in web
32
- interface, simply install the Gollum gem, navigate to your repository via the
31
+ To view your RTFMd repository locally via the built in web
32
+ interface, simply install the RTFMd gem, navigate to your repository via the
33
33
  command line, and run the executable:
34
34
 
35
- bin/golem
35
+ bin/rtfmd
36
36
 
37
- This will start up a web server running the Gollum frontend and you can view
37
+ This will start up a web server running the RTFMd frontend and you can view
38
38
  your wiki at http://localhost:3000
39
39
 
40
40
  ## REPO STRUCTURE
41
41
 
42
- A Gollum repository's contents are designed to be human editable. Page content
42
+ A RTFMd repository's contents are designed to be human editable. Page content
43
43
  is written in `page files` and may be organized into directories any way you
44
44
  choose. Special footers can be created in `footer files`. Other content
45
45
  (images, PDFs, etc) may also be present and organized in the same way.
@@ -52,7 +52,7 @@ Page files may be written in Markdown with extensions:
52
52
  * Markdown: .mkd, .markdown, .mdown, .mkdn, .md
53
53
  * ronn: .ronn
54
54
 
55
- Gollum detects the page file format via the extension, so files must have one
55
+ RTFMd detects the page file format via the extension, so files must have one
56
56
  of the supported extensions in order to be converted.
57
57
 
58
58
  Page file names may contain any printable UTF-8 character except space
@@ -85,7 +85,7 @@ subdirectories that do not have a footer file of their own.
85
85
 
86
86
  ## HTML SANITIZATION
87
87
 
88
- For security and compatibility reasons Gollum wikis may not contain custom CSS
88
+ For security and compatibility reasons RTFMd wikis may not contain custom CSS
89
89
  or JavaScript. These tags will be stripped from the converted HTML. See
90
90
  `docs/sanitization.mkd` for more details on what tags and attributes are
91
91
  allowed.
@@ -93,7 +93,7 @@ allowed.
93
93
 
94
94
  ## BRACKET TAGS
95
95
 
96
- A variety of Gollum tags use a double bracket syntax. For example:
96
+ A variety of RTFMd tags use a double bracket syntax. For example:
97
97
 
98
98
  [[Link]]
99
99
 
@@ -114,7 +114,7 @@ Some formats, such as MediaWiki, support the opposite syntax:
114
114
 
115
115
  ## PAGE LINKS
116
116
 
117
- To link to another Gollum wiki page, use the Gollum Page Link Tag.
117
+ To link to another RTFMd wiki page, use the RTFMd Page Link Tag.
118
118
 
119
119
  [[Frodo Baggins]]
120
120
 
@@ -133,7 +133,7 @@ page name, you can specify the actual page name after a pipe:
133
133
  The above tag will link to `Frodo-Baggins.mkd` using "Frodo" as the link text.
134
134
 
135
135
  The page file may exist anywhere in the directory structure of the repository.
136
- Gollum does a breadth first search and uses the first match that it finds.
136
+ RTFMd does a breadth first search and uses the first match that it finds.
137
137
 
138
138
  Here are a few more examples:
139
139
 
@@ -156,17 +156,17 @@ underlying markup format.
156
156
 
157
157
  ## ABSOLUTE VS. RELATIVE VS. EXTERNAL PATH
158
158
 
159
- For Gollum tags that operate on static files (images, PDFs, etc), the paths
159
+ For RTFMd tags that operate on static files (images, PDFs, etc), the paths
160
160
  may be referenced as either relative, absolute, or external. Relative paths
161
161
  point to a static file relative to the page file within the directory
162
- structure of the Gollum repo (even though after conversion, all page files
162
+ structure of the RTFMd repo (even though after conversion, all page files
163
163
  appear to be top level). These paths are NOT prefixed with a slash. For
164
164
  example:
165
165
 
166
166
  gollum.pdf
167
167
  docs/diagram.png
168
168
 
169
- Absolute paths point to a static file relative to the Gollum repo's
169
+ Absolute paths point to a static file relative to the RTFMd repo's
170
170
  root, regardless of where the page file is stored within the directory
171
171
  structure. These paths ARE prefixed with a slash. For example:
172
172
 
@@ -185,10 +185,10 @@ whatever works best in your situation.
185
185
 
186
186
  ## FILE LINKS
187
187
 
188
- To link to static files that are contained in the Gollum repository you should
189
- use the Gollum File Link Tag.
188
+ To link to static files that are contained in the RTFMd repository you should
189
+ use the RTFMd File Link Tag.
190
190
 
191
- [[Gollum|gollum.pdf]]
191
+ [[RTFMd|gollum.pdf]]
192
192
 
193
193
  The first part of the tag is the link text. The path to the file appears after
194
194
  the pipe.
@@ -196,8 +196,8 @@ the pipe.
196
196
 
197
197
  ## IMAGES
198
198
 
199
- To display images that are contained in the Gollum repository you should use
200
- the Gollum Image Tag. This will display the actual image on the page.
199
+ To display images that are contained in the RTFMd repository you should use
200
+ the RTFMd Image Tag. This will display the actual image on the page.
201
201
 
202
202
  [[gollum.png]]
203
203
 
@@ -206,13 +206,13 @@ can specify between pipe delimiters.
206
206
 
207
207
  To specify alt text, use the `alt=` option. Default is no alt text.
208
208
 
209
- [[gollum.png|alt=Gollum and his precious wiki]]
209
+ [[gollum.png|alt=RTFMd and his precious wiki]]
210
210
 
211
211
  To place the image in a frame, use the `frame` option. When combined with the
212
212
  `alt=` option, the alt text will be used as a caption as well. Default is no
213
213
  frame.
214
214
 
215
- [[gollum.png|frame|alt=Gollum and his precious wiki]]
215
+ [[gollum.png|frame|alt=RTFMd and his precious wiki]]
216
216
 
217
217
  To specify the alignment of the image on the page, use the `align=` option.
218
218
  Possible values are `left`, `center`, and `right`. Default is `left`.
@@ -279,7 +279,7 @@ line.
279
279
 
280
280
  ## API DOCUMENTATION
281
281
 
282
- The Gollum API allows you to retrieve raw or formatted wiki content from a Git
282
+ The RTFMd API allows you to retrieve raw or formatted wiki content from a Git
283
283
  repository, write new content to the repository, and collect various meta data
284
284
  about the wiki as a whole.
285
285
 
@@ -288,7 +288,7 @@ Initialize the Gollum::Repo object:
288
288
  # Require rubygems if necessary
289
289
  require 'rubygems'
290
290
 
291
- # Require the Gollum library
291
+ # Require the RTFMd library
292
292
  require 'gollum'
293
293
 
294
294
  # Create a new Gollum::Wiki object by initializing it with the path to the
@@ -4,7 +4,7 @@ Gem::Specification.new do |s|
4
4
  s.rubygems_version = '1.3.5'
5
5
 
6
6
  s.name = 'RTFMd'
7
- s.version = '0.10301.1'
7
+ s.version = '0.10301.2'
8
8
  s.date = '2011-12-16'
9
9
 
10
10
  s.summary = "A simple, Markdown documentation helper."
@@ -45,6 +45,7 @@ Gem::Specification.new do |s|
45
45
  README.md
46
46
  Rakefile
47
47
  bin/rtfm
48
+ bin/rtfmd
48
49
  docs/sanitization.md
49
50
  RTFMd.gemspec
50
51
  lib/gollum.rb
data/bin/rtfm CHANGED
@@ -1,12 +0,0 @@
1
- #!/bin/bash -e
2
-
3
- if [[ -n $1 ]]; then
4
- GOLEM_WIKI=$1; shift
5
- else
6
- GOLEM_WIKI=$(pwd)
7
- fi
8
-
9
- export GOLEM_WIKI
10
-
11
- bundle check 2>&- || { bundle install --local && bundle check; }
12
- exec bundle exec thin start -R config/golem.ru
@@ -0,0 +1,12 @@
1
+ #!/bin/bash -e
2
+
3
+ if [[ -n $1 ]]; then
4
+ GOLEM_WIKI=$1; shift
5
+ else
6
+ GOLEM_WIKI=$(pwd)
7
+ fi
8
+
9
+ export GOLEM_WIKI
10
+
11
+ bundle check 2>&- || { bundle install --local && bundle check; }
12
+ exec bundle exec thin start -R config/golem.ru
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: RTFMd
3
3
  version: !ruby/object:Gem::Version
4
- hash: 41193
4
+ hash: 41199
5
5
  prerelease:
6
6
  segments:
7
7
  - 0
8
8
  - 10301
9
- - 1
10
- version: 0.10301.1
9
+ - 2
10
+ version: 0.10301.2
11
11
  platform: ruby
12
12
  authors:
13
13
  - Tom Bombadil
@@ -292,6 +292,7 @@ files:
292
292
  - README.md
293
293
  - Rakefile
294
294
  - bin/rtfm
295
+ - bin/rtfmd
295
296
  - docs/sanitization.md
296
297
  - RTFMd.gemspec
297
298
  - lib/gollum.rb