SwiftBar VS fastapi

I don't know if this supports your use case, but look into SwiftBar. https://github.com/swiftbar/SwiftBar

I’m in a similar boat. Only one external monitor on an M1 Studio. Every time I restart, GeekTool cannot find the monitor, so I have to manually move all 10 of my geeklets to the main monitor. I looked into moving them via script, but was unsuccessful because the monitor id was inexplicably not identical on geektool’s side between launches (I gather this is a known issue from the developer). Sadly, I have been unable to find an app that sufficiently replicates GeekTools functionality. That being said, I have moved some of my scripts to SwiftBar where they are accessible via the menu bar instead of displayed on the desktop. Works fine for simple text stuff, but not my more graphical calendar. I’m saving this post though, because I still want a true fix/replacement for GeekTool.

https://github.com/swiftbar/SwiftBar - Powerful macOS menu bar customization tool

As many of you, I obsess over the current metrics of my TMHI modem. Opening the app to check it is too cumbersome. On MacOS there is a cool free utility that allows simple scripts to run in the menu called SwiftBar (get it here: https://github.com/swiftbar/SwiftBar )

Maybe swiftbar?

I am sure you could create a stock ticker with SwiftBar https://swiftbar.app. SwiftBar has plugins which write to the menubar using shell scripts. And there are already some stock ticker plugins - I am sure you could modify one of them to meet your needs.

That’s when I found FastAPI.

FastAPI & Uvicorn

Discussion at FastAPI GitHub: https://github.com/tiangolo/fastapi/issues/2696

An API application framework (such as FastAPI)

It’s been my experience that async Python frameworks tend to turn IO bound problems into CPU bound problems with a high enough request rate, because due to their nature they act as unbounded queues.

This ends up made worse if you’re using sync routes.

If you’re constrained on a resource such as a database connection pool, your framework will continue to pull http requests off the wire that a sane client will cancel and retry due to timeouts because it takes too long to get a connection out of the pool. Since there isn’t a straightforward way to cancel the execution of a route handler in every Python http framework I’ve seen exhibit this problem, the problem quickly snowballs.

This is an issue with fastapi, too- https://github.com/tiangolo/fastapi/issues/5759

Fast API.

We will create our API using FastAPI, a modern high-performance web framework for building fast APIs with Python. It is designed to be easy to use, efficient, and highly scalable. Some key features of FastAPI include:

FastAPI is a modern, fast, web framework for building APIs with Python 3.7+ based on standard Python type hints. It is designed to be easy to use, fast to run, and secure. In this blog post, we’ll explore the key features of FastAPI and walk through the process of creating a simple API using this powerful framework.

FastAPI is a modern, fast web framework for building APIs with Python 3.7+ that automatically generates OpenAPI and JSON Schema documentation. While FastAPI simplifies API development, manually creating and updating API documentation can still be a time-consuming task. In this blog post, we’ll explore how to leverage FastAPI’s automatic documentation generation capabilities, specifically focusing on Swagger and ReDoc, and how to streamline the process of documenting your APIs.