website/integrations: Pocketbase

[nicedevil007]

Heya @4d62,

here is my try on getting the "regular" PocketBase Documentation done.
This was suggested as better usecase for authentik vs. PocketBase in general than just creating the same documenation for all Pocketbase applications over and over again.

With this guide we can reference all those applications to this one here :)

This was done prior to this guide where the idea came up: #12905

---

Checklist

• Local tests pass (ak test authentik/)
• The code has been formatted (make lint-fix)

If an API change has been made

• The API schema has been updated (make gen-build)

If changes to the frontend have been made

• [] The code has been formatted (make web)

If applicable

• The documentation has been updated
• The documentation has been formatted (make website)

[netlify]

✅ Deploy Preview for authentik-docs ready!

Name	Link
🔨 Latest commit	458720b
🔍 Latest deploy log	https://app.netlify.com/sites/authentik-docs/deploys/679f355a309e4c00086ce34e
😎 Deploy Preview	https://deploy-preview-12906--authentik-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for authentik-storybook canceled.

Name	Link
🔨 Latest commit	458720b
🔍 Latest deploy log	https://app.netlify.com/sites/authentik-storybook/deploys/679f355afbfa230007995e9a

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.67%. Comparing base (7c944b9) to head (458720b).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12906      +/-   ##
==========================================
- Coverage   92.75%   92.67%   -0.09%     
==========================================
  Files         769      770       +1     
  Lines       38929    38945      +16     
==========================================
- Hits        36109    36092      -17     
- Misses       2820     2853      +33     

Flag	Coverage Δ
e2e	48.46% <ø> (-0.11%)	⬇️
integration	24.59% <ø> (-0.02%)	⬇️
unit	90.37% <ø> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dominic-r]

Hi @nicedevil007, thanks for your contibution. It is greatly appreciated. Here are a few things I noticed. Please do let me know if you have any questions.

[dominic-r]

Note to tana: This should be left as-is for now and I'll update format /button names later on.

[dominic-r]

I don't see anything in this redirect URI that would warrant it to be set to "regex" instead of "strict". It's best to set it to "strict" unless absolutely needed.

[nicedevil007]

Hi and thank you for your Review. Maybe it my wrong understanding of the Wiki about contribution but I used all "placeholder variables" in italic Font. I switched between different Write options now through my last PRs and Never know what is wanted and what Not.

Can someone clear this up?

• bold stuff for things on the SP side that can be found on the gui f.e.
• itatlic for placeholders

That is what I understood so far. Now it seems to be yet another new formatation here. I get more and more confused.

[dominic-r]

The Fonts & Fonts styling section of our style guide gives an overview of what's expected. What do you mean by "new formatation here"?

Italic is to be used for variables, yes. Bold for stuff found in the GUI, yes. URLs should be in a codeblock and variables in them should be italicized and the easiest way to do that is the suggestion I gave.

[nicedevil007]

I mean this Part of the Guide

Use italic font for variables or placeholders to make it clear they need to be replaced. Choose placeholder names that highlight their purpose, ensuring users understand what to update.

---

Thank you for making this clear now :) So I can Go oder my last PRs to Match this Styling :) Will take a Bit of time, but I Like have it "the same" on everything

[dominic-r]

Could you also address the original review comment? Thanks

I don't see anything in this redirect URI that would warrant it to be set to "regex" instead of "strict". It's best to set it to "strict" unless absolutely needed.

[nicedevil007]

Maybe I copy Pasted wrong line and it was Late at Night. Will get to it tomorrow. But I guess you are right :)

[nicedevil007]

So I always wrote it like the menu entry is in authentik:

"Redirect URIs/Origins (RegEx)" is the setting we have to set. But it doesn't mean that we should choose RegEx on the dropdown, so how should I do it now?