View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004449 | Taler | exchange | public | 2016-04-19 15:27 | 2016-05-05 15:42 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.0 | ||||
| Target Version | 0.0 | Fixed in Version | 0.0 | ||
| Summary | 0004449: we need a way to automatically generate a configuration for testing | ||||
| Description | That includes generating keys, signing wire response, ... We don't want to have them somewhere as binary files, since it needs to be understandable how they can be generated. This includes the config for the exchange as well as for the merchant. Basically we should have a script $ taler-config-generate that generates a reasonable configuration for testing in the XDG-appropriate directories and files. | ||||
| Tags | No tags attached. | ||||
| related to | 0004460 | closed | Marcello Stanisci | simplify taler installation process |
| Actually, most of this should simply be done by having good defaults in config.d/. The only thing we cannot cover by defaults (AFAIK) are bank/wire setup and coin configuration. The proposed tool could auto-generate a canonical coin specification, i.e. by being given the currency (--currency=EUR), and maybe simplify the bank setup (--wire=test --bank-url=http://localhost:8080/). Invoking taler-exchange-keyup is then a trivial step. | |
| I agree with your suggestion. The existing deployments by now rely heavily on the defaults, only key setup / wire confirm is tedious. | |
| Another step is missing: For the exchange we need to generate the private (offline signing) key first, since the corresponding public key needs to be in the exchange configuration. | |
| taler-config-generate implemented and documented (with man page) in 6040ada..07d9978. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-04-19 15:27 | Florian Dold | New Issue | |
| 2016-04-19 15:27 | Florian Dold | Status | new => assigned |
| 2016-04-19 15:27 | Florian Dold | Assigned To | => Christian Grothoff |
| 2016-04-22 17:41 | Florian Dold | Relationship added | related to 0004460 |
| 2016-04-24 21:48 | Christian Grothoff | Priority | normal => low |
| 2016-04-24 21:48 | Christian Grothoff | Severity | minor => feature |
| 2016-04-24 21:48 | Christian Grothoff | Product Version | => 0.0 |
| 2016-04-30 12:49 | Christian Grothoff | Note Added: 0010582 | |
| 2016-04-30 12:49 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2016-04-30 12:49 | Christian Grothoff | Status | assigned => implementing |
| 2016-04-30 12:49 | Christian Grothoff | Target Version | => 0.2 |
| 2016-04-30 12:55 | Florian Dold | Note Added: 0010587 | |
| 2016-05-02 08:21 | Florian Dold | Note Added: 0010601 | |
| 2016-05-04 04:47 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2016-05-04 04:47 | Christian Grothoff | Status | implementing => assigned |
| 2016-05-05 13:40 | Christian Grothoff | Priority | low => normal |
| 2016-05-05 15:42 | Christian Grothoff | Note Added: 0010650 | |
| 2016-05-05 15:42 | Christian Grothoff | Status | assigned => informing |
| 2016-05-05 15:42 | Christian Grothoff | Fixed in Version | => 0.0 |
| 2016-05-05 15:42 | Christian Grothoff | Resolution | open => fixed |
| 2016-05-05 15:42 | Christian Grothoff | Status | informing => closed |
| 2016-05-05 15:42 | Christian Grothoff | Target Version | 0.2 => 0.0 |