forked from beaker-project/beaker-project.org
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
52 lines (35 loc) · 1.77 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
This is the beaker-project.org web site.
To make changes, edit the relevant file and then run `make` to update
the generated files. You must have a clean, up-to-date checkout of the
master branch of Beaker's git for the documentation to be built. The
Makefile assumes Beaker can be found in ../beaker; if not, you must pass
the path in the BEAKER variable, e.g. `make BEAKER=/home/dan/beaker`.
Note that many parts of this web site are generated from elsewhere:
* Some .html pages are generated from the corresponding .txt file in
Markdown using Pandoc.
* Some documentation is built using Sphinx from docstrings extracted
from Beaker code.
* Some documentation is built using Publican from DocBook sources
included in Beaker.
* Some shell scripts have a pretty documented version which is
generated by shocco.
Publishing the web site
-----------------------
These instructions are only relevant to Beaker developers who have
access to publish to beaker-project.org.
Only publish changes that are already on the master branch. Make sure
your master branch is up to date:
git checkout master
git pull
Also make sure your 'published' branch is up to date. This is a special
branch for tracking the published version of the web site (including all
generated artefacts):
git fetch beaker-project.org:/srv/www/beaker-project.org/git/ master:published
Build your changes:
make publish
Now the 'published' branch has been updated. You may want to push it to
http://stage.beaker-project.org/ first, to make sure everything looks
okay:
git push beaker-project.org:/srv/www/stage.beaker-project.org/git/ published:master
Once you're happy with it, push it live:
git push beaker-project.org:/srv/www/beaker-project.org/git/ published:master