You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2024. It is now read-only.
Would be fantastic if doctree serve could use s3 as filesystem backend - would allow me to use doctree index in CI and upload the files to s3 where they could be served, allowing a central highly-available doctree frontend for all projects
Thanks for filing this! I can't say for sure right now if this will make sense or not. The reason being: search.
I really need to figure out how to do good/nice search indexing for the docs, and that will likely involve leveraging local SSD performance (otherwise it'd require a lot of memory.)
I do think finding a way for this to be super simple to deploy, easily turned into an HA service, and (most importantly) easy to keep your projects indexed is extremely important though.
I'll keep this issue open and revisit once I have a better idea of how search in doctree will look / be implemented.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey!
Would be fantastic if
doctree serve
could use s3 as filesystem backend - would allow me to usedoctree index
in CI and upload the files to s3 where they could be served, allowing a central highly-available doctree frontend for all projectsMaybe via a filesystem abstraction layer like https://github.com/usmanhalalit/gost , https://github.com/lytics/cloudstorage , https://github.com/graymeta/stow
Note: my use-case only covers frontend part, assuming i can s3 upload the indexed file to the right path and it would just work
The text was updated successfully, but these errors were encountered: