Test "write" API access, website currently using "read" API token
Implement Auth layer (would rather use an IDp like Google or GitHub) as don't want GDPR hassle with storing personal details
Configure something like OAuth2Proxy to handle the Auth flow
Add "Edit Tag" UI and backend logic. Needs to check forwarded Auth headers to see if logged in etc
Haven't forgotten about this.
There's a few parts to this:
* Test "write" API access, website currently using "read" API token
* Implement Auth layer (would rather use an IDp like Google or GitHub) as don't want GDPR hassle with storing personal details
* Configure something like OAuth2Proxy to handle the Auth flow
* Add "Edit Tag" UI and backend logic. Needs to check forwarded Auth headers to see if logged in etc
<!-- github-comment-id:3733055347 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We need a protected gui to update user profiles and node details.
Haven't forgotten about this.
There's a few parts to this:
I think the current solution is good enough for now. Closing.