Skip to content
This repository was archived by the owner on Jun 7, 2023. It is now read-only.

Commit d815871

Browse files
committed
tasks to do in order to use this version of the tools
1 parent 1b2a257 commit d815871

File tree

1 file changed

+51
-0
lines changed

1 file changed

+51
-0
lines changed

README.md

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,3 +2,54 @@ RunestoneTools
22
==============
33

44
Packaging of the Runestone tools for publishing educational materials using github pages
5+
6+
During January 2014 I switched my personal blog to OctoPress. This inspired me in many ways. First to try to blog more often, but more importantly to think about how the Runestone Toolset could be more easily used and deployed by people who didn't want to mess around with hosting, and setting up web2py servers, etc. This new project is the first phase of that inspiration.
7+
8+
Prerequisites
9+
-------------
10+
11+
The following three prerequisites are easily installed using pip. All are either Python2.x or 3.x compatible.
12+
13+
1. Install Spinx
14+
2. Install Paver
15+
3. Install paverutils
16+
17+
18+
::
19+
First get `Sphinx <http://sphinx.pocoo.org>`_, version 1.1.x is current as of this writing:
20+
21+
# pip install sphinx
22+
23+
Install `paver <http://paver.github.io/paver/>`_, at least version 1.2.0:
24+
25+
::
26+
27+
# pip install paver
28+
29+
30+
Once paver is installed you will also need to install sphinxcontrib-paverutils, at least version 1.5:
31+
32+
::
33+
34+
# pip install sphinxcontrib-paverutils
35+
36+
Publishing your own materials with Runestone
37+
--------------------------------------------
38+
39+
1. Clone the RunestoneTools repository to your development machine
40+
2. Create a repository (if you don't already have one where you would like to host the finished product)
41+
3. paver build
42+
4. cd build
43+
5. git init
44+
5. git remote add origin [email protected]:bnmnetp/deploytest.git
45+
5. git checkout -b gh-pages
46+
5. git touch .nojekyll
47+
5. git add .nojekyll
48+
5. git add .
49+
6. git commit -m 'first published version'
50+
7. git push origin gh-pages
51+
52+
Now wait a few minutes and go to http://username.github.io/yourRepo
53+
54+
You should see an example page.
55+

0 commit comments

Comments
 (0)