exchange/src/exchangedb/test-exchange-db-postgres.conf

[exchange]
#The DB plugin to use
DB = postgres

[exchangedb-postgres]

#The connection string the plugin has to use for connecting to the database
CONFIG = postgres:///talercheck


[exchangedb]

# After how long do we close idle reserves?  The exchange
# and the auditor must agree on this value.  We currently
# expect it to be globally defined for the whole system,
# as there is no way for wallets to query this value.  Thus,
# it is only configurable for testing, and should be treated
# as constant in production.
IDLE_RESERVE_EXPIRATION_TIME = 4 weeks

# After how long do we forget about reserves?  Should be above
# the legal expiration timeframe of withdrawn coins.
LEGAL_RESERVE_EXPIRATION_TIME = 7 years
renaming mint->exchange 2016-03-01 15:35:04 +01:00			`[exchange]`
db: pick the right plugin in the DB testcase 2015-03-26 18:31:59 +01:00			`#The DB plugin to use`
			`DB = postgres`

renaming mint->exchange 2016-03-01 15:35:04 +01:00			`[exchangedb-postgres]`
fix #3835 2015-06-11 16:11:07 +02:00
db: pick the right plugin in the DB testcase 2015-03-26 18:31:59 +01:00			`#The connection string the plugin has to use for connecting to the database`
Changing configuration structure to enable multiple accounts. This change enables using multiple wire plugins at the same time. Also, we now distinguish between the wire plugin (i.e. EBICS or taler_bank) and the wire method (i.e. SEPA or x-taler-bank) that the wire plugin is implementing. The "taler-bank" wire method was renamed from "test" to "x-taler-bank". This also changes the format of the /wire response of the exchange, as we now need to return multiple accounts. Note that wire fees are specified per wire method, not per wire account. taler-exchange-keyup now automatically signs all of the /wire responses in the location specified by the configuration. Account identification in wire plugins was changed to use payto://-URLs instead of method-specific JSON fields. Signing and validation of /wire responses was moved from each wire plugin to a generic validation method in libtalerutil (crypto) or libtalerjson (for JSON-formatted inputs). Convenience methods were added to generate JSON for wire accounts (salting, signing). Various section and option names were adjusted to streamline the configuration and make it more consistent overall. Documentation was updated as well. 2018-04-02 14:24:45 +02:00			`CONFIG = postgres:///talercheck`
finished implementing #4956 in principle, but not yet tested 2017-04-20 21:38:02 +02:00

			`[exchangedb]`

			`# After how long do we close idle reserves? The exchange`
			`# and the auditor must agree on this value. We currently`
			`# expect it to be globally defined for the whole system,`
			`# as there is no way for wallets to query this value. Thus,`
			`# it is only configurable for testing, and should be treated`
			`# as constant in production.`
			`IDLE_RESERVE_EXPIRATION_TIME = 4 weeks`
make sure reserves are not gc'ed before legal expiration 2019-07-24 12:19:36 +02:00
			`# After how long do we forget about reserves? Should be above`
			`# the legal expiration timeframe of withdrawn coins.`
			`LEGAL_RESERVE_EXPIRATION_TIME = 7 years`