Currently we support file:// and http{s}:// handlers on the CLI. We could equally support entrypoint-like specifications, much like fastapi run can do. This would allow maximum configuration of the repository, whilst not having to worry about the other details (like setting up the fast api app itself).

The logic would be:

• If it starts with http:// or https:// it is a http repo
• If it starts with file:// or the thing is an existing path, then use Local
• Otherwise, follow the entrypoint value definition of load (https://github.com/python/cpython/blob/fa6dbb16419dacb57cb831b1fac5a32fef4f412d/Lib/importlib/metadata/__init__.py#L173) such that we get a callable which returns the repository

This might minimise the need to create a bespoke FastAPI app (e.g. in astrofrog/pypi-timemachine#32, though in that case we do actually want to influence the endpoints which are exposed...)