gidget 0.0.8 → 0.0.9
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/README.rdoc +27 -14
- data/_stub_/Gemfile +1 -0
- metadata +3 -3
data/README.rdoc
CHANGED
@@ -1,8 +1,8 @@
|
|
1
1
|
= gidget
|
2
2
|
|
3
|
-
|
3
|
+
_The smallest taco-loving blog engine in the world!_ (anyone remember 'Yo quiero Taco Bell'?)
|
4
4
|
|
5
|
-
Gidget is a minimalist blog engine designed to run on Heroku with a Git-based workflow. It is built upon Sinatra and uses
|
5
|
+
Gidget is a minimalist blog engine designed to run on Heroku with a Git-based workflow. It is built upon Sinatra and uses haml and rdiscount for templating and markup. It was largely inspired by Toto, however Gidget is built on top of a DSL to minimize and simplify the code.
|
6
6
|
|
7
7
|
== Basic Structure
|
8
8
|
|
@@ -25,33 +25,46 @@ Posts are simply .txt files located under a folder named posts located off the r
|
|
25
25
|
|
26
26
|
title: My great post title
|
27
27
|
date: 2010-11-19
|
28
|
+
|
29
|
+
_Hello World!_ This is my first blog post!
|
28
30
|
|
29
31
|
The second section is the body of the post and uses markdown as it's markup language. The two sections should be separated by an empty line.
|
30
32
|
|
31
|
-
File name and structure (other than the .txt extension) don't matter. Gidget will determine request paths
|
32
|
-
|
33
|
-
== Heroku
|
34
|
-
|
35
|
-
Gidget is meant to run on a Heroku. It offers version management through Git, and uses the advantages provided by running behind a reverse-proxy cache such as Varnish. Gidget is meant to be minimalist in design while taking these factors into consideration.
|
33
|
+
File name and structure (other than the .txt extension) don't matter. Gidget will determine request paths based on the date and title metadata and sort them accordingly.
|
36
34
|
|
37
35
|
== Getting Started
|
38
36
|
|
39
|
-
|
37
|
+
The following comands install the Gidget gem, create a Gidget app, and then start the app:
|
40
38
|
|
41
39
|
gem install gidget
|
40
|
+
gidget my-gidget-app
|
41
|
+
cd my-gidget-app
|
42
|
+
rackup
|
42
43
|
|
43
|
-
|
44
|
+
At this point you should be able to view your blog by visiting: http://localhost:9292
|
44
45
|
|
45
|
-
|
46
|
+
== Adding Source Control
|
46
47
|
|
47
|
-
|
48
|
+
Before you can host yoru app on Heroku, you must be using Git for source control. Run the following from your app directory to create a new git repository and add all your app code to it:
|
48
49
|
|
49
|
-
|
50
|
-
|
50
|
+
git init
|
51
|
+
git add *
|
52
|
+
git commit -a -m "Initial load"
|
53
|
+
|
54
|
+
== Deploy To Heroku
|
55
|
+
|
56
|
+
In order to deploy an app to Heroku you must have an account with them. Once you have your account, deploying to Heroku is super easy thanks to their gem:
|
57
|
+
|
58
|
+
gem install heroku
|
59
|
+
heroku create
|
60
|
+
git push heroku master
|
61
|
+
heroku open
|
62
|
+
|
63
|
+
Congrats! You now have your own blog running on the internets!
|
51
64
|
|
52
65
|
== TO BE DONE
|
53
66
|
|
54
|
-
*
|
67
|
+
* Possibly add a paging route to allow /page/1 type usage. Need to determine best way of handling options/setting such as page_size.
|
55
68
|
|
56
69
|
== Contributing to gidget
|
57
70
|
|
data/_stub_/Gemfile
CHANGED
metadata
CHANGED
@@ -1,13 +1,13 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: gidget
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
hash:
|
4
|
+
hash: 13
|
5
5
|
prerelease: false
|
6
6
|
segments:
|
7
7
|
- 0
|
8
8
|
- 0
|
9
|
-
-
|
10
|
-
version: 0.0.
|
9
|
+
- 9
|
10
|
+
version: 0.0.9
|
11
11
|
platform: ruby
|
12
12
|
authors:
|
13
13
|
- Forrest Robertson
|