View Issue Details

IDProjectCategoryView StatusLast Update
0004460Talerotherpublic2018-04-15 18:34
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
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionopen 
Product Version0.0 
Target Version0.5Fixed in Version0.5 
Summary0004460: simplify taler installation process
DescriptionWhen applying changes to the configuration and key file structure to the test deployment together with Marcello, we were a bit surprised about the amount of time it takes to set up the configuration from scratch, even for Taler core developers.

We should make a few things more consistent and user friendly, and especially work towards having saner defaults. Also better error messages would help in a lot of cases.

See related bugs for concrete examples of what should be improved or problems that occured.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

related to 0004447 closedFlorian Dold move arm-related things from deployment.git to the respective taler repos 
related to 0004458 closedFlorian Dold exchange-specific configuration sections and files have too generic names 
related to 0004461 closedChristian Grothoff configuration creates keys if they don't exist without complaining 
related to 0004462 closedChristian Grothoff syntax for temporary table creation different for merchant and exchange; semantics not clearly documented 
related to 0004448 closedFlorian Dold wire configuration is redundant 
related to 0004449 closedChristian Grothoff we need a way to automatically generate a configuration for testing 

Activities

Christian Grothoff

2017-11-04 17:40

manager   ~0012559

Given how quickly Marcello managed the 0.4 demo update and that most of the sub-bugs are resolved, I think we can call this one resolved for now.

Issue History

Date ModifiedUsernameFieldChange
2016-04-22 14:02Florian DoldNew Issue
2016-04-22 14:02Florian DoldRelationship addedrelated to 0004439
2016-04-22 14:03Florian DoldRelationship addedrelated to 0004447
2016-04-22 14:03Florian DoldRelationship addedrelated to 0004458
2016-04-22 14:03Florian DoldRelationship addedrelated to 0004105
2016-04-22 14:06Florian DoldDescription Updated
2016-04-22 14:07Florian DoldDescription Updated
2016-04-22 14:09Florian DoldRelationship addedrelated to 0004461
2016-04-22 14:10Florian DoldRelationship addedrelated to 0004462
2016-04-22 15:18Florian DoldRelationship addedrelated to 0004448
2016-04-22 17:41Florian DoldRelationship addedrelated to 0004449
2016-04-24 21:58Christian GrothoffSeverityminor => feature
2016-04-24 21:58Christian GrothoffProduct Version => 0.0
2016-05-05 13:26Christian GrothoffStatusnew => acknowledged
2016-05-05 13:26Christian GrothoffTarget Version => 0.5
2017-03-18 23:08Christian GrothoffTarget Version0.5 => 0.7.1
2017-11-04 17:39Christian GrothoffRelationship deletedrelated to 0004439
2017-11-04 17:39Christian GrothoffRelationship deletedrelated to 0004105
2017-11-04 17:40Christian GrothoffAssigned To => Marcello Stanisci
2017-11-04 17:40Christian GrothoffStatusacknowledged => informing
2017-11-04 17:40Christian GrothoffFixed in Version => 0.5
2017-11-04 17:40Christian GrothoffTarget Version0.7.1 => 0.5
2017-11-04 17:40Christian GrothoffNote Added: 0012559
2018-04-15 18:34Christian GrothoffStatusinforming => closed