Skip to content

Conversation

@edan-bainglass
Copy link
Member

@edan-bainglass edan-bainglass commented Dec 2, 2025

Based on #96

Supersedes #65

This PR takes a different approach to #65. It implements a read-only API by way of separating read/write endpoints to read/write routers, only serving the former in --read-only mode.

The PR also adds a CLI for easy API launch.

Closes #63
Closes #86

@edan-bainglass
Copy link
Member Author

Note to self - also hide login endpoint

@edan-bainglass
Copy link
Member Author

@superstar54 you had mentioned a native FAST API way to do this. The documentation does not describe a native approach to this. There are suggestions online, some involving middleware. However, such a method aims to disable write routes. I chose to instead remove them entirely from the API on --read-only, to more explicitly communicate that they "do not exist" or unavailable in read-only mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Read-only version Add concept of read-only endpoints and add configuration to block anything but read-only endpoints

1 participant