mirror of
https://github.com/YunoHost-Apps/glitchsoc_ynh.git
synced 2024-09-03 19:15:59 +02:00
33 lines
1.6 KiB
Markdown
33 lines
1.6 KiB
Markdown
|
## Administrate with tooctl
|
||
|
|
|
||
|
|
`$ (cd /var/www/glitchsoc/live && sudo -u glitchsoc RAILS_ENV=production PATH=/opt/rbenv/versions/glitchsoc/bin bin/tootctl --help)`
|
||
|
|
|
||
|
|
## Update
|
||
|
|
|
||
|
|
**`screen` (or `tmux`) can be used to make sure your session is not interrupted in case of connection problems.**
|
||
|
|
See [tutorial](https://www.howtogeek.com/662422/how-to-use-linuxs-screen-command/) for more background information.
|
||
|
|
|
||
|
|
```
|
||
|
|
$ screen
|
||
|
|
$ sudo yunohost app upgrade glitchsoc
|
||
|
|
```
|
||
|
|
|
||
|
|
## Backups
|
||
|
|
|
||
|
|
First of all: Glitch-Soc uses a local cache to save media (such as posted images, videos etc.). This cache can grow huge.
|
||
|
|
You could consider cleaning up your local cache first as otherwise your backup will be very big and you might run out of disk space:
|
||
|
|
|
||
|
|
To check your space usage, on a command line run:
|
||
|
|
|
||
|
|
`$ sudo cd /var/www/glitchsoc/live && sudo -u glitchsoc RAILS_ENV=production PATH=/opt/rbenv/versions/glitchsoc/bin bin/tootctl media usage`
|
||
|
|
|
||
|
|
If your cache is too big to backup, you can run the following command to clean up Attachments (the first line). Substitute X by the number of days you want to keep, e.g. 1 day. All older images will be deleted but will be refetched from the original server if necessary.
|
||
|
|
|
||
|
|
First dry-run to see how much space is freed up (without actually removing):
|
||
|
|
|
||
|
|
`$ sudo cd /var/www/glitchsoc/live && sudo -u glitchsoc RAILS_ENV=production PATH=/opt/rbenv/versions/glitchsoc/bin bin/tootctl media remove --days=X --dry-run`
|
||
|
|
|
||
|
|
If all looks good commit the cleanup:
|
||
|
|
|
||
|
|
`$ sudo cd /var/www/glitchsoc/live && sudo -u glitchsoc RAILS_ENV=production PATH=/opt/rbenv/versions/glitchsoc/bin bin/tootctl media remove --days=X `
|