retoor/devplacepy
1
0
Fork 1
Code Issues 1 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

feat: add six specialized Claude agent definitions under .claude/agents for audit, devii, docs, dry, fanout, and frontend maintenance

Browse Source
This commit is contained in:
retoor
2026-06-13 18:34:47 +00:00
parent ede7a863b7
commit de745f7a75
107 changed files with 2611 additions and 517 deletions
Download Patch File Download Diff File Expand all files Collapse all files
devplacepy/templates/docs/authentication.html
+11 -13
View File
@@ -3,12 +3,11 @@
<div class="docs-content" data-render>
# Authentication
DevPlace accepts four interchangeable authentication methods. The session cookie is
used by the website; the other three let you authenticate **any request** - any
page or action - without logging in through the browser, which is ideal for scripts
and automation. See also [Conventions & Errors](/docs/conventions.html) for the base
URL, request bodies, content negotiation, pagination, and status codes that every
endpoint shares.
DevPlace accepts four interchangeable authentication methods. The website uses the
session cookie; the other three authenticate **any request** - any page or action -
without a browser login, ideal for scripts and automation. See
[Conventions & Errors](/docs/conventions.html) for the base URL, request bodies,
content negotiation, pagination, and status codes that every endpoint shares.
{% if not user %}
> You are not logged in. Examples below use placeholders. [Log in](/auth/login) and
@@ -24,7 +23,7 @@ You can regenerate it there at any time; the previous key stops working immediat
The interactive panels throughout the [API reference](/docs/index.html) pre-fill your API
key, so you can run user-level calls directly from these pages. Vote, reaction, bookmark, and
poll endpoints require an `X-Requested-With: fetch` header to return JSON instead of a
redirect; the panels and generated snippets add it for you.
redirect; the panels and generated snippets add it automatically.
## 1. Session cookie
@@ -42,8 +41,7 @@ curl -H "X-API-KEY: {{ api_key }}" \
## 3. Bearer token
The same API key also works as a Bearer token, which many HTTP clients support out
of the box:
The same API key also works as a Bearer token, supported out of the box by many HTTP clients:
```bash
curl -H "Authorization: Bearer {{ api_key }}" \
@@ -87,8 +85,8 @@ curl -X POST -H "X-API-KEY: {{ api_key }}" \
## Errors
If you supply credentials that are invalid, protected endpoints respond with
`401 Unauthorized`. Requests with no credentials at all are treated as anonymous
(and protected actions redirect to the login page, as in the browser). The full
status-code and error-shape reference lives in [Conventions & Errors](/docs/conventions.html).
Invalid credentials make protected endpoints respond with `401 Unauthorized`. Requests
with no credentials are treated as anonymous, and protected actions redirect to the login
page as in the browser. The full status-code and error-shape reference lives in
[Conventions & Errors](/docs/conventions.html).
</div>