mirror of
https://git.qoto.org/m33/misskey-admin-scripts-n-tips.git
synced 2024-10-22 23:19:08 +00:00
Update README.md
This commit is contained in:
parent
a08e935fc4
commit
0f17e458c7
1 changed files with 11 additions and 2 deletions
13
README.md
13
README.md
|
@ -44,10 +44,19 @@ Deploying your misskey instance on arm64 using docker is pretty straightforward,
|
|||
|
||||
# Scripts list:
|
||||
|
||||
## start_misskey.sh stop_misskey.sh update_misskey.sh
|
||||
In a small VPS, or a limited computer like the rapsberry, or just because systemd, you may want to start stop and update misskey with simple scripts like this.
|
||||
## start_misskey.sh stop_misskey.sh
|
||||
In a small VPS, or a limited computer like the rapsberry, or just because systemd, you may want to start and stop misskey with simple scripts like this.
|
||||
For automatic start on boot, you may add this to your crontab: `@reboot /usr/local/bin/start_misskey.sh 1>>/var/log/syslog 2>&1`
|
||||
|
||||
## check_update_misskey_git.sh
|
||||
This script tries to determine if an update is needed, without pulling all source code from Misskey's github depot.
|
||||
Return 1 if an update is detected.
|
||||
|
||||
## update_misskey.sh
|
||||
Handles the grunt work for a git update, and containers rebuild.
|
||||
It takes care of code base backup, you really should take care of database (and maybe data files) backup before upgrading. To this day Misskey updates have not always been a smooth road.
|
||||
It may automatically restart your instance to apply the update.
|
||||
|
||||
## backup_postgres.sh
|
||||
A daily backup for your docker postgresql database, run it daily
|
||||
It will cycle with the day of week (1..7)
|
||||
|
|
Loading…
Reference in a new issue