diff options
| author |  tobi <31960611+tsmethurst@users.noreply.github.com> | 2024-09-28 16:58:39 +0200 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2024-09-28 16:58:39 +0200 |
| commit | 7978d88a01c3f868ff49a3510464ee4f5a9b92a7 (patch) | |
| tree | cf27bc41bc58b7d03f3515ff799261157fac8d46 /docs/advanced | |
| parent | update modernc/sqlite to v1.33.1 (with our concurrency workaround) (#3367) (diff) | |
| download | gotosocial-7978d88a01c3f868ff49a3510464ee4f5a9b92a7.tar.xz | |
[chore] Update apparmor example file (#3368)
Diffstat (limited to 'docs/advanced')
| -rw-r--r-- | docs/advanced/security/sandboxing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/advanced/security/sandboxing.md b/docs/advanced/security/sandboxing.md index 067940e32..41b9f2eb3 100644 --- a/docs/advanced/security/sandboxing.md +++ b/docs/advanced/security/sandboxing.md @@ -24,7 +24,7 @@ $ sudo apparmor_parser -Kr /etc/apparmor.d/gotosocial ``` !!! tip - If you're using SQLite, the AppArmor profile expects the database in `/gotosocial/db/` so you'll need to adjust your configuration paths or the policy accordingly. + The provided AppArmor example is just intended to get you started. It will still need to be edited depending on your exact setup; consult the comments in the example profile file for more information. With the policy installed, you'll need to configure your system to use it to constrain the permissions GoToSocial has. |