manuscript 0.1.1 → 0.1.2
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 +11 -0
- data/VERSION +1 -1
- data/manuscript.gemspec +1 -1
- metadata +1 -1
data/README.rdoc
CHANGED
|
@@ -41,6 +41,7 @@ In the repository directory, edit the file called <tt>config.ru</tt> to match yo
|
|
|
41
41
|
ActiveRecord::Base.establish_connection :adapter => 'sqlite3', :database => 'manuscript.sqlite3.db'
|
|
42
42
|
|
|
43
43
|
use Rack::Session::Cookie
|
|
44
|
+
use Rack::Static, :urls => ["/template_files"]
|
|
44
45
|
use Gatekeeper::Middleware do |sso|
|
|
45
46
|
sso.sso_url = "http://hotink.theorem.ca/sso"
|
|
46
47
|
end
|
|
@@ -60,6 +61,16 @@ You can then deploy this like any other Rack app. You can even test it out:
|
|
|
60
61
|
|
|
61
62
|
To start settings things up, visit "/admin" from your application's host and port.
|
|
62
63
|
|
|
64
|
+
=== A cleaner setup
|
|
65
|
+
|
|
66
|
+
While you can deploy a Manuscript as indicated above, if you don't want to clone a repository onto your production machine you have another option. Simply
|
|
67
|
+
prepare an sqlite3 database on you local machine, in a cloned Manuscript repository.
|
|
68
|
+
|
|
69
|
+
Make sure the <b>gem is installed</b> on your production machine, then create a new directory and create a <tt>rackup.ru</tt> file and make it read as
|
|
70
|
+
shown above.
|
|
71
|
+
|
|
72
|
+
Template files will be saved into a directory '/template_files' alongside <tt>config.ru</tt>. They'll also be served from there. Now deploy away.
|
|
73
|
+
|
|
63
74
|
== Note on Patches/Pull Requests
|
|
64
75
|
|
|
65
76
|
* Fork the project.
|
data/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
0.1.
|
|
1
|
+
0.1.2
|
data/manuscript.gemspec
CHANGED