Use /var/tmp for media cache path #776
No reviewers
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#776
Loading…
Reference in a new issue
No description provided.
Delete branch "norm/akkoma:nginx-var-tmp"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The /var/tmp directory is not mounted as tmpfs unlike /tmp which is
mounted as such on some distros like Fedora or Arch. Since there isn't
really a benefit to having the cache on tmpfs, this change should allow
for a larger cache if needed without worrying about running out of RAM.
The old path is also referenced in
docs/docs/configuration/howto_mediaproxy.md
docs/docs/configuration/onion_federation.md
docs/docs/configuration/i2p.md
installation/apache/akkoma-apache.conf
installation/apache/apache-cache-purge.sh
The latter two being from Apache but the use of
cache_disk__module
seems to suggest it too is fine or even expects cache being backed by a regular disk0aab2d6ee6
toace3fac890
Use /var/tmp for nginx cache pathto Use /var/tmp for media cache path@ -29,3 +10,1 @@
```
If you came here from one of the installation guides, take a look at the example configuration `/installation/nginx/akkoma.nginx`, where this part is already included.
* This is _required_; we do not support using the same domain as the main instance due to past security bugs.
it’s technically not required (but strongly recommended), Akkoma "just" hurls a warning at you on each start if
base_url
belongs to the instance domain (settingbase_url
is now required though)@ -157,2 +133,3 @@
In the Nginx config, add the following into the `location /` block:
```nginx
add_header X-XSS-Protection "0";
I like cutting this down to only the bits relevant to i2p, but the old config also changed the listening port (presumably to match i2p convention or some other part of this guide). This probably should still be mentioned
@ -101,2 +77,3 @@
In the Nginx config, add the following into the `location /` block:
```nginx
add_header X-XSS-Protection "0";
same thing as with i2p
ace3fac890
to1cb814feee
Not sure about moving and changing
to
But otherwise good
1cb814feee
tobb29c5bed2
I've changed it back to the old wording
huh, TIL
is all coolio, thanks!