When running FastAPI app, all the logs in console are from Uvicorn and they do not have timestamp and other useful information. As Uvicorn applies python logging module, we can override Uvicorn logging formatter by applying a new logging configuration.
Meanwhile, it's able to unify the your endpoints logging with the Uvicorn logging by configuring all of them in the config file log_conf.yaml.
Before overriding:
uvicorn main:app --reload
| while True: | |
| try: | |
| x = int(input("How long do you want your popper to be? ").strip()) | |
| break | |
| except ValueError: | |
| print("Not an int") | |
| continue | |
| s = input("what should your custom word be? ") |
| version: '3.4' | |
| services: | |
| sql.data: | |
| image: mcr.microsoft.com/mssql/server:2017-latest | |
| container_name: dev_sql | |
| environment: | |
| - SA_PASSWORD=yourStrong(!)Password | |
| - ACCEPT_EULA=Y | |
| healthcheck: |
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions and generate verion and changelogs
| local state, data, reactor, turbine, info_window, rules_window | |
| local STATES = { | |
| READY = 1, -- Reactor is off and can be started with the lever | |
| RUNNING = 2, -- Reactor is running and all rules are met | |
| ESTOP = 3, -- Reactor is stopped due to rule(s) being violated | |
| UNKNOWN = 4, -- Reactor or turbine peripherals are missing | |
| } | |
| ------------------------------------------------ |
In the apps config/puma.rb file:
Change to match your CPU core count
# Check using this on the server => grep -c processor /proc/cpuinfo
workers 4
# Min and Max threads per worker
threads 1, 6
app_dir = File.expand_path('../..', FILE)