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 Feb 1, 2018. It is now read-only.
How hard would it be to add a basic authentication layer? (ie: for documenting private git-hub projects on a GitHub pages site)
I realise the published documentation content/back-end files could still be accessed by an unauthenticated user by guessing their URLs, but a simple authentication mechanism on the front-end SPA would be sufficiently-secure for many private projects.
Ideally, authentication linked to GitHub would be awesome if it allowed access to the published documentation based on a user's permission to access the underlying documentation's GitHub repo.
(This is something I would be interested in contributing to, since most documentation systems are focused on public vs private documentation, and I'm still looking for a GitHub-centric alternative for documenting our team's private projects. )
Regards, Michael
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How hard would it be to add a basic authentication layer? (ie: for documenting private git-hub projects on a GitHub pages site)
I realise the published documentation content/back-end files could still be accessed by an unauthenticated user by guessing their URLs, but a simple authentication mechanism on the front-end SPA would be sufficiently-secure for many private projects.
Ideally, authentication linked to GitHub would be awesome if it allowed access to the published documentation based on a user's permission to access the underlying documentation's GitHub repo.
(This is something I would be interested in contributing to, since most documentation systems are focused on public vs private documentation, and I'm still looking for a GitHub-centric alternative for documenting our team's private projects. )
Regards, Michael
The text was updated successfully, but these errors were encountered: