Vlastimil Zíma

As a middle step, I would propose to translate current `Setting` to accept annotation-style type argument to check the value against, i.e. add `type` argument (find better name if possible)...

"invite only" is part of a Login section settings. I'm not very familiar with Discourse, but I haven't found any other solution. To the proposed fix: indeed, I'd like all...

I got back to this, since my workaround was removed after an update. * `auth_skip_create_confirm` was disabled. * `force_https` was enabled. Still no idea, why it doesn't work.

> how would appending work for a boolean flag? Indeed, that wouldn't work and I am OK with that :-) I'm not suggesting that override should _always_ append, but that...

I can confirm that Discourse works correctly once downgraded back to `2.8.14~ynh1`. The downgrade itself isn't easy. Downgrade workflow: 1. Make discourse backup (from the discourse itself, not the Yunohost)...

Any comments on this? Otherwise, I'd start with first steps to deprecate it.

The idea is to transform the default always, unless the `call_default` is `True`. I intent to keep the possibility of a callable default.

Seems I will need to solve #37 first.

The problem is not is cache, but in environment variables. ```python # ATTR=terminal with override_settings(ATTR='Override1'): # Override shifts the environment: __DAP_ATTR=terminal, ATTR not defined print(S.attr) # output: Override1 [correct] with...

I think about something like: ```python class Settings(object): default_default_value = None def __init__(self, ..., default=NOT_PROVIDED, ...): @property def default_value(self): if self.default == NOT_PROVIDED: return self.default_default_value # Give or take the...