View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010973 | Taler | merchant backend | public | 2026-02-04 15:11 | 2026-02-04 15:11 |
| Reporter | Florian Dold | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Summary | 0010973: merchant backend configuration structure in Debian package is not sensible | ||||
| Description | We have the following structure in /etc/taler-merchant/: taler-merchant.conf: Main entry point, that's fine overrides.conf: Fine, used by NetzBon tooling conf.d/*: These files are included by taler-merchant.conf, fine conf.d/merchant.conf: This one is problematic: - Why are these settings not in taler-merchant.config? It seems like it has the DB configuration, so IMO the name should indicate that - It includes a ../merchant-overrides.conf. Why is that file included by conf.d/merchant.conf?! - It's a drop-in file where the order matters, thus it should have a name like `50-merchantdb.conf`, otherwise the load order is hard to understand. merchant-overrides.conf: Why is this file required at all?! Super misleading, as the way it's included does not even mean it has highest precedence. Overall, it is not sensible which files an admin setting up the merchant should actually edit or create. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-02-04 15:11 | Florian Dold | New Issue |
