Conversation
|
set to draft as we're awaiting feedback for #46 |
|
also contemplating if this should be blocked by #70 as I feel rate limits may be one of the main reasons to self host, so having this documented is definitely a must |
|
As mentioned by @dealloc in #72, the While it's easily possible to take the OpenAPI spec at It's not a major concern, but it would save some clicks when the API changes. Thanks for the great work on the |
that was an easy fix, 1ae220f should address this by just copying all openapi files rather than just the spec files |
|
as confirmed in #46 (comment) and #72 this PR is now available for review 🥳 |
Where is the SwaggerUI available under?
Build log also looks suspiciously empty: |
|
oops, looks like that's on me |
|
@stnokott could you verify if the last 2 commits fixed the issue of Swagger not being available? |
Fixed! All my needs are satisfied now 😄 |
|
Thanks for the swift fixes! |
|
@chatterchats looks this is all ready for you then! |
Allow Dockerfile to specify whether to copy the OpenAPI specs
chatterchats
left a comment
There was a problem hiding this comment.
Ayo, documentation? Imagine!

This PR adds additional documentation for running the application in Docker/Podman containers.
It also adds a build flag to the Dockerfile so that OpenAPI support (Swagger and JSON files) can be bundled in the container (off by default, since we don't serve it on the hosted version)