-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing hidden folders with RTD #585
Conversation
Hmmm for some reason it is correctly finding the HTML, but not actually replacing it with the encrypted version. https://readthedocs.org/projects/2i2c-team-compass/builds/18882723/ EDIT: Indeed this is a known bug: |
📰 We've done some progress on the |
Hi @choldgraf 👋🏼 . I followed your example to test this out and I got it working at https://test-builds.readthedocs.io/en/staticrypt/ (password is |
@humitos it worked! |
Great! 💯 I'm curious about what's the use-case behind this idea about using On the other hand, on Read the Docs for Business, a similar feature is already built-in in the platform: https://docs.readthedocs.io/en/stable/commercial/sharing.html
|
In our case, I'm auto-generating dashboards about 2i2c's upstream activity as well as some financial activity with Jupyter Book. The data is not publicly accessible, and some of the dashboards might have sensitive information in them. So the source files don't have anything sensitive, but the built outputs do, which is why I wanted to put them behind a password. |
@choldgraf is this a PR to close? |
@consideRatio yeah let's close it, was a little experiment but I'm not sure if/when we'll get to it so we can always re-open if need be |
This is just me playing around with staticrypt to learn more about it.
I think I may have found a bug in RTD? I opened this one to ask about it: