Frank Elsinga

We don't assign users to issues. Firstly, because I can only assign the issue poster and contributors and secondly because I don't think that bureaucracy is nessesary ^^ Just drop...

> with an issue link which has more deep/detail information about this bug. Seems we have no such a link about this by now. Linking this very issue -> https://github.com/maplibre/martin/issues/1651#issuecomment-2628674788...

Your English is excellent, no complaints/.. there. Don't worry about that ever ^^ (To be fair: it is also not a native language for me)

Since We added a warning for postgis

How did you deploy to kubernetes? What is the file system you use? (NFS is not compatible with SQLite3 due to bad locking) There are a lot of issues that...

I think the discussion in said thread has so far been "not invented here", so no technical reason why there is a new spec. Without there being a reson for...

@nyurik Would you consider a migration to [`tracing`](https://docs.rs/tracing)? I think that would give us the flexibility needed to configure this as needed.. As a default, I think pretty in development...

That does work, but changing all the log imports from `use log::*` -> `use tracing::*` allows further functionality down the line: 

Shure, can look into it. Looking at the docks, this seems simple: [](https://docs.rs/tracing/latest/tracing/#log-compatibility)

> yaml: > ```yaml > log_format: json|pretty|compact > ``` Actually: lets scrap this part. and stick to the current support (env variables only for configuring logging) We want to use...