openproject

Commit Graph

Author	SHA1	Message	Date
Christophe Bliard	48a4f1b6ad	lint with rubocop --autocorrect (safe cops only)	2 years ago
Christophe Bliard	126fab49ba	add setting:available_envs rake task to list overridable env var names	3 years ago
ulferts	d63586bbc9	define aliases for smtp/mail definitions Removes the automatic prefixing of env_alias to allow for a greater flexibility. That way, the email settings can be unprefixed as well as prefixed and the 2FA will always be prefixed	3 years ago
Christophe Bliard	ba0361c37f	override value from unprefixed env only for used-to-be configuration settings	3 years ago
Christophe Bliard	7d0d812b35	remove deprecation warning when using nested hash in env var names	3 years ago
Christophe Bliard	73a8421c42	make nested hash env names work with env_alias for Setting	3 years ago
Christophe Bliard	2c67f992a5	stringify hash settings keys and support OPENPROJECT_2FA env var updated code to look up the string key instead of the symbol key introduce a 'with settings' rspec shared context	3 years ago
Christophe Bliard	8082cd9d08	log deprecation warning when using env var names to set nested hash setting	3 years ago
Christophe Bliard	e02df3f29d	handle env vars overriding hash setting with single underscore setting OPENPROJECT_REPOSITORY_CHECKOUT_DATA_GIT_MINIMUM__VERSION=42 will do the same as OPENPROJECT_REPOSITORY__CHECKOUT__DATA_GIT_MINIMUM__VERSION=42: it will do Setting.repository_checkout_data['git']['minimum_data'] = 1 Please use OPENPROJECT_REPOSITORY_CHECKOUT_DATA='{git: {minimum_version: 42}}' instead, it is more readable.	3 years ago
Christophe Bliard	9f498b2f8e	load settings from variations of env variables could load value from: - OPENPROJECT_SOME__KEY__NAME=value can now also load value from: - OPENPROJECT_SOME_KEY_NAME=value - SOME_KEY_NAME=value A deprecation message is logged if used without the OPENPROJECT_ prefix.	3 years ago
ulferts	285650e6c3	allow have dates parsed from file and env	3 years ago
ulferts	a734ed8b80	shift overriding setting values to when a setting is defined	3 years ago
ulferts	0b5575aa64	harmonize settings & configuration They are for now still available as separate entities but that is more due to existing references to them both. Under the hood, they now depend on the same structure `Settings::Definition` which just as well could have been named `Configuration::Definition`, that defines: * the name * the default value * the type (which might be deferred from the default value) * the array of allowed values Both Setting and Configuration can now be overwritten using the same mechanisms: * Default value * Database value * configuration.yml (settings.yml is removed) * ENV vars	3 years ago

13 Commits (0acfcfd9eb54df12850a4d2991cf0551a0d53636)