summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2017-10-17 10:00:29 +0200
committerChristian Grothoff <christian@grothoff.org>2017-10-17 10:00:29 +0200
commitf6dcc192cf28d794793bb26fae99317922834c81 (patch)
treee52a3e6bf8f2cefe0be118d00ca070ecab274f56 /doc
parent875611776203727de67974a933144070c54b216b (diff)
downloaddeployment-f6dcc192cf28d794793bb26fae99317922834c81.tar.gz
deployment-f6dcc192cf28d794793bb26fae99317922834c81.tar.bz2
deployment-f6dcc192cf28d794793bb26fae99317922834c81.zip
fix subsectioning, top-level needs to be chapter
Diffstat (limited to 'doc')
-rw-r--r--doc/onboarding.texi40
1 files changed, 20 insertions, 20 deletions
diff --git a/doc/onboarding.texi b/doc/onboarding.texi
index 8840570..93e3aff 100644
--- a/doc/onboarding.texi
+++ b/doc/onboarding.texi
@@ -57,9 +57,9 @@ Texts. A copy of the license is included in the section entitled
@end menu
@node Taler.net
-@section Taler.net
+@chapter Taler.net
-@subsection Git
+@section Git
Git at @code{taler.net} is managed by @emph{gitolite}. Creation and deletion
of repositories, as well as users management, is done entirely by editing the
@@ -71,7 +71,7 @@ Please refer to gitolite official documentation, if more information is needed:
This section documents the set-up of our main server @code{taler.net}.
-@subsection Buildbot
+@section Buildbot
@quotation Note
'worker' and 'slave' are used interchangeably
@@ -79,7 +79,7 @@ This section documents the set-up of our main server @code{taler.net}.
The user running the buildbot master is @emph{containers}.
-@subsubsection Master
+@subsection Master
To start the master, log in as @emph{containers}, and run:
@@ -104,7 +104,7 @@ $ source ~/buildbot/venv/bin/activate
$ buildbot reconfig ~/buildbot/master/
@end example
-@subsubsection Documentation worker
+@subsection Documentation worker
This worker is responsible for building all the documentation on
@code{https://docs.taler.net}. It is run by the user @code{docbuilder},
@@ -141,7 +141,7 @@ and this makes generated files unreadable.
@end quotation
@end cartouche
-@subsubsection Wallet worker
+@subsection Wallet worker
This worker is responsible for running wallet testcases. It is run
by the @emph{containers} user. Manage this worker with the following
commands:
@@ -157,7 +157,7 @@ $ buildbot-worker stop ~/buildbot/wallet_worker/
$ deactivate
@end example
-@subsubsection Selenium worker
+@subsection Selenium worker
This worker is responsible for running the Selenium wallet test:
an automatic clicker that performs the cycle withdraw-and-spend.
@@ -177,7 +177,7 @@ $ buildbot-worker stop ~/buildbot/selenium_worker/
$ deactivate
@end example
-@subsubsection Lcov worker
+@subsection Lcov worker
The worker is implemented by the @emph{lcovslave} user and is responsible
for generating the HTML showing the coverage of our tests, then available
@@ -208,7 +208,7 @@ $ taler-deployment-arm -k taler-postgres-standalone
$ taler-deployment-arm -e
@end example
-@subsubsection Switcher worker
+@subsection Switcher worker
Taler.net uses a "blue/green" fashion to update the code it
uses in demos. Practically, there are two users: @emph{test-green}
@@ -242,13 +242,13 @@ $ buildbot-worker stop ~/buildbot/slave
$ deactivate
@end example
-@subsubsection Manual switch
+@subsection Manual switch
After the desired blue/green party has been compiled, it is possible to
log-in as @emph{test} and run the script @code{$HOME/.ln-<COLOR>.sh}, in order to make
@code{test-<COLOR>} active.
-@subsubsection Website lcov.taler.net
+@subsection Website lcov.taler.net
The directory @code{/var/www/lcov.taler.net} contains the following two symlinks
@@ -261,7 +261,7 @@ The pointed locations are updated by the @emph{lcovslave}.
@node Standalone deployment
-@section Standalone deployment
+@chapter Standalone deployment
This tecnique aims to set a thorough Taler installation up on a
@@ -415,7 +415,7 @@ at @code{<DEPLOYMENT-REPO>/etc/nginx}.
@end cartouche
@node Deployment on demo.taler.net
-@section Deployment on demo.taler.net
+@chapter Deployment on demo.taler.net
This section describes how to upgrade the whole Taler setup on the
@url{taler.net} Web site. Here, the deployment scripts include a
@@ -493,9 +493,9 @@ $ taler-deployment-start
Now the symlink can be updated.
@node Releases
-@section Releases
+@chapter Releases
-@subsection Release Process and Checklists
+@section Release Process and Checklists
This document describes the process for releasing a new version of the various
Taler components to the official GNU mirrors.
@@ -510,7 +510,7 @@ The following components are published on the GNU mirrors
@item taler-wallet-webex (wallet-webex.git)
@end itemize
-@subsection Tagging
+@section Tagging
Tag releases with an @b{annotated} commit, like
@@ -519,13 +519,13 @@ git tag -a v0.1.0 -m "Official release v0.1.0"
git push origin v0.1.0
@end example
-@subsection Database for tests
+@section Database for tests
For tests in the exchange and merchant to run, make sure that
a database @emph{talertest} is accessible by @emph{$USER}. Otherwise tests
involving the database logic are skipped.
-@subsection Exchange, merchant
+@section Exchange, merchant
Set the version in @code{configure.ac}. The commit being tagged
should be the change of the version.
@@ -544,7 +544,7 @@ make install check
@end example
-@subsection Wallet WebExtension
+@section Wallet WebExtension
The version of the wallet is in @emph{manifest.json}. The @code{version_name} should be
adjusted, and @emph{version} should be increased independently on every upload to
@@ -558,7 +558,7 @@ make dist
@c FIXME: selenium test cases
-@subsection Upload to GNU mirrors
+@section Upload to GNU mirrors
See @emph{https://www.gnu.org/prep/maintain/maintain.html#Automated-FTP-Uploads}