View Issue Details

IDProjectCategoryView StatusLast Update
0004359Talerdocumentationpublic2017-10-23 08:52
ReporterFlorian Dold Assigned ToMarcello Stanisci Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeveritytextReproducibilityhave not tried
Status closedResolutionopen 
Product Version0.0 
Target Version0.5Fixed in Version0.4 
Summary0004359: document taler.net setup
DescriptionWe need to have some documentation on what's running on taler.net, in case the server crashes and burns and we need to set up a new one.

Part of that configuration (like nginx, and the demo/test account setup) is already in the deployment.git, but we should describe other important parts of the setup as well.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

related to 0004645 closedChristian Grothoff Refactor of Taler API's documentation 

Activities

Marcello Stanisci

2016-11-10 10:01

reporter   ~0011469

Last edited: 2016-12-20 10:48

Buildbot: master is 'containers' user and there are two workers which are 'bbslave' (just build the whoe codebase) and 'lcosvslave' (generates lcov HTML, therefore referenced by lcov.taler.net).

To start the master: from container's $HOME, execute buildbot/start.sh
To stop the master: from container's $HOME, execute buildbot/stop.sh
(A restart.sh is also available in the same location)

To start the slave: from whatever slave's $HOME, execute
  
  $ . activate
  $ taler-deployment-bbstart
  # To stop it
  $ taler-deployment-bbstop

Marcello Stanisci

2016-11-10 10:03

reporter   ~0011470

Florian: whenever you think something is worth documenting, leave a note on that.

Marcello Stanisci

2016-12-23 11:30

reporter   ~0011609

How to run and stop docker images. Look at README in deployment/docker/README.

Marcello Stanisci

2017-04-23 08:59

reporter   ~0012057

deployment's repository tracks a txt called tripwire_sysadmin.txt, where all
(?) the instructions about running services on tripwire are collected.

Christian Grothoff

2017-10-23 08:52

manager   ~0012511

We have the onboarding manual, so this is no longer an outstanding issue. Naturally, it is an _ongoing_ issue to keep everything documented and improving the docs, but the specific original issue of having _some_ docs is clearly fixed.

Issue History

Date ModifiedUsernameFieldChange
2016-04-04 12:16Florian DoldNew Issue
2016-04-06 07:42Christian GrothoffSeverityminor => text
2016-04-06 07:42Christian GrothoffStatusnew => implementing
2016-04-06 07:42Christian GrothoffCategoryother => deployment and operations
2016-04-06 07:42Christian GrothoffProduct Version => 0.0
2016-05-05 13:29Christian GrothoffTarget Version => 0.5
2016-05-26 19:57Christian GrothoffTarget Version0.5 => 0.1
2016-05-26 19:59Christian GrothoffAssigned To => Marcello Stanisci
2016-05-26 19:59Christian GrothoffStatusimplementing => assigned
2016-05-31 07:50Christian GrothoffTarget Version0.1 => 0.4
2016-09-07 14:57Marcello StanisciRelationship addedrelated to 0004645
2016-10-10 06:33Christian GrothoffTarget Version0.4 => 0.5
2016-11-07 08:59Marcello StanisciCategorydeployment and operations => documentation
2016-11-10 10:01Marcello StanisciNote Added: 0011469
2016-11-10 10:03Marcello StanisciNote Added: 0011470
2016-11-16 14:07Marcello StanisciNote Edited: 0011469
2016-12-20 10:32Marcello StanisciNote Edited: 0011469
2016-12-20 10:48Marcello StanisciNote Edited: 0011469
2016-12-23 11:30Marcello StanisciNote Added: 0011609
2017-04-08 22:16Christian GrothoffTarget Version0.5 => 0.7.1
2017-04-23 08:59Marcello StanisciNote Added: 0012057
2017-10-23 08:52Christian GrothoffStatusassigned => closed
2017-10-23 08:52Christian GrothoffFixed in Version => 0.4
2017-10-23 08:52Christian GrothoffTarget Version0.7.1 => 0.5
2017-10-23 08:52Christian GrothoffNote Added: 0012511