10 years ago, I made the first commit on #dynaconf - The #Python configuration library
https://github.com/dynaconf/dynaconf/commits/master/?since=2015-08-14&until=2015-08-15
10 years ago, I made the first commit on #dynaconf - The #Python configuration library
https://github.com/dynaconf/dynaconf/commits/master/?since=2015-08-14&until=2015-08-15
How LocalStack uses #Dynaconf to manage AWS Boto configurations
https://blog.localstack.cloud/2024-05-08-building-localstack-with-localstack/
We are increasingly building various parts of the LocalStack Web Application using our core cloud emulator, leveraging numerous features for local cloud development. In this blog, we share how we are dogfooding our software to promote faster feature development and reduce inefficient testing loops.
Taigram: как мы решали проблемы данных и пришли к бете
Продолжаем рассказывать о разработке нашего Open Source проекта Taigram . В этой статье мы поделимся тем, как организовали конфигурацию приложения, решили проблемы с запуском в разных окружениях и как справлялись с потоком уведомлений. Также затронем тему бета-тестирования и расскажем, как вы можете помочь нам сделать Taigram лучше.
https://habr.com/ru/articles/891290/
#open_source #python #dynaconf #fastapi #aiogram #taiga #taigram #lifespan #json
Taigram: Архитектура приложения
Всем привет! Мы продолжаем работу над нашим Open Source проектом Taigram! Прошлая статья "Taigram: Начало работы" , можно сказать, была посвящена организационным моментам:
https://habr.com/ru/articles/887172/
#python #taiga #aiogram #fastapi #telegram #dynaconf #github #actions #yaml #ci_cd
New feature coming to #python #dynaconf tomorrow!
dynaconf debug-info is a new command, similar to the existing inspect command but as a summary.
feat: Add CLI command debug-info by rochacbruno · Pull Request #1251 · dynaconf/dynaconf https://github.com/dynaconf/dynaconf/pull/1251
Here is how to read #1password secrets on your #Python program using #Dynaconf
You can extend Dynaconf converters and route the load to external tool.
# settings.toml
PASSWORD = "@op op://Vault/namespace/password"
# python
print(settings.PASSWORD) # password from 1password
For Dynaconf 4.0 we are planning a general @secret op://|bw://|vault:// converter that will parse the protocol.
I really like the new script metadata and UV supports it, so I will update ALL my projects documentation examples to use uv run as the default runner.
Much easier than asking people to create a virtualenv and activate it.
BTW: #Dynaconf is a #Python library I maintain, it loads settings from various sources and parses, merges, validates it, It can be integrated with #Flask, #Django, #FastAPI and supports reading settings from #Redis or #Hashicorp #Vault, or even custom storages.
A simple 2 line change made a huge difference on the time taken to instantiate Dynaconf with the merging of 14 yaml files and 44 validators.
Hi everyone, I filled up 35 RFCs on #python #dynaconf for 3.3.0 and 4.0.0 (breaking) so open to hear comments, suggestions, objections.
This work will shape the future of Dynaconf and open the possibility to fix the flaws we have in the current design.
We finally added typed settings to #python #dynaconf, it uses Typing Annotations to declare defaults and Validators.
Instead of using #Pydantic we decided to go with a simpler solution that is not a breaking change to our current Validator implementation.
So this feature is still tech-preview, there are more details to implement such as subtypes and #django compatibility.