FZambia
commented
1 month ago During last two weeks I was working on Centrifugo v6. The focus in v6 is configuration refactoring - make it unified, structured, more explicit.
In the current state it's becoming very hard to maintain and add new features – so as part of Centrifugo v6 implementing the configuration framework which is simple to read and extend in the code. Also, I want to provide a unified way to set secrets for all entities inside arrays - like inside list of proxies, list of consumers configuration. And a unified config key validation (shown now as warnings on Centrifugo v5 start).
To show one example how config will change, this is what we could have in Centrifugo v5 now:
{
"token_hmac_secret_key": "XXX",
"admin_password": "XXX",
"admin_secret": "XXX",
"api_key": "XXX",
"allowed_origins": ["http://localhost:3000"],
"presence": true,
"namespaces": [
{"name": "ns", "presence": true}
]
}In Centrifugo v6 becomes:
{
"client": {
"token": {
"hmac_secret_key": "XXX"
},
"allowed_origins": [
"http://localhost:3000"
]
},
"admin": {
"password": "XXX",
"secret": "XXX"
},
"http_api": {
"key": "XXX"
},
"channel": {
"without_namespace": {
"presence": true
},
"namespaces": [
{
"name": "ns",
"presence": true
}
]
}
}Or in YAML:
---
client:
token:
hmac_secret_key: XXX
allowed_origins:
- http://localhost:3000
admin:
password: XXX
secret: XXX
http_api:
key: XXX
channel:
without_namespace:
presence: true
namespaces:
- name: ns
presence: trueOnly top-level structure is different, nested keys like channel options stay the same. In the code configuration will be a single readable Go struct instead of manually crafted (using viper key getters) different structs.
matsuev
This is an issue to collect information about Centrifugo v6 in one place. There is no date for the release defined yet. This post will be updated.