Djeex/docudjeex
1
1
Fork 0
Code Issues Pull Requests Projects Wiki Activity

Add step-by-step TinyAuth protection sections across the guides

Browse Source
This commit is contained in:
Djeex
2026-09-02 19:28:22 +02:00
parent 1117ff1827
commit bb8581a535
12 changed files with 802 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/3.serveex/3.security/4.tinyauth.md
+2 -2
View File
@@ -143,7 +143,7 @@ Here we assume the TinyAuth network name is `tinyauth_default`. You can check th
In the Swag folders, create the file `tinyauth.subdomain.conf`:
::tip{icon=""}
✨ __Tip:__ Use [File Browser](/serveex/files/file-browser) to navigate and edit files instead of using terminal commands.
✨ __Tip:__ Use [File Browser Quantum](/serveex/files/file-browser-quantum) to navigate and edit files instead of using terminal commands.
::
```bash [Terminal]
@@ -295,7 +295,7 @@ server {
::note
The `location /tinyauth` block must be able to reach the TinyAuth container by its Docker name (`tinyauth` here). Add TinyAuth's network to this stack's compose file the same way you did [for Swag](/serveex/security/tinyauth#exposing-tinyauth-with-swag) if it isn't already attached.
The `location /tinyauth` block runs inside SWAG's own container, so SWAG needs to be on TinyAuth's Docker network to reach it by name (`tinyauth` here). This should already be set up from [exposing TinyAuth itself](/serveex/security/tinyauth#exposing-tinyauth-with-swag). If you run into an error, double-check SWAG's compose file still has that network attached.
::
Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ctrl+X"} to exit.