wsdd VS fastapi

https://github.com/christgau/wsdd/blob/master/README.md https://bugzilla.samba.org/show\_bug.cgi?id=11473

`--net=host` will connect container to hosts stack (it becomes hosts). without it container connects to `bride` network thus requiring exclusive port forward. See wsdd section firewall setup and you may like to revist following

You can install this on your RPi to be able to discover them: https://github.com/christgau/wsdd

Windows stopped using NetBIOS ever since they deprecated SMB1. It uses Web Service Dynamic Discovery (WS-Discovery). If your server is running Linux, you can install a 3rd party daemon to add WS-Discovery support. See here for more background.

Microsoft changed* how SMB network discovery works. To get my Raspberry Pi running RasPiOS to show up on the network I have to install the Windows Network Discovery Daemon

That's interesting although I'm not a Mac user OMV uses wsdd and has therefore made things easier on a windows network. I think, but I can't confirm you can deploy wsdd on a Mac would that solve it......just a thought

If you check out the WSDD python script in the askubuntu link ( https://github.com/christgau/wsdd ) it can make the samba server visible in "network".

Install wsdd on the Pi - https://github.com/christgau/wsdd

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.

TiTiler is a dynamic tile server built on FastAPI and Rasterio/GDAL. Its main features include support for Cloud Optimized GeoTIFF(COG), multiple projection methods, various output formats (JPEG, JP2, PNG, WEBP, GTIFF, NumpyTile), WMTS, and virtual mosaic. It also provides Lambda and ECS deployment environments using AWS CDK.

To make it a bit more realistic, we’re going to use a FastAPI route as an example, and we’re also going to use FastAPI’s dependency injection, which can really help with readability (and testability, but more on that later).

2. FastAPI - Turbocharge Your Web APIs with Python ⚡