Garbaye/services-garbaye
3
1
Fork 0
Code Issues 5 Pull requests Packages Projects Releases Wiki Activity
services-garbaye/podman-seafile
History
Gitouche 9770535d1c Seafile : websocket
2023-06-15 22:30:05 +02:00
..
.gitlab-ci.yml Seafile : suppression variables propres à la qualif et/ou mauvais defaults (Garbaye) 2023-02-10 16:04:40 +01:00
00_status.sh refactoring scripts identiques : pod status 2022-01-28 13:37:31 +01:00
05_freshinstall.sh framadate, jitsi, seafile : appel de 10_install dans 05_freshinstall, comme matrix 2022-01-28 22:28:12 +01:00
10_install.sh Seafile : websocket 2023-06-15 22:30:05 +02:00
20_enable.sh refactoring scripts identiques : pod enable 2022-01-28 13:15:48 +01:00
30_start.sh refactoring scripts identiques : pod start 2022-01-28 13:19:53 +01:00
40_stop.sh refactoring scripts identiques : pod stop 2022-01-28 13:23:34 +01:00
70_disable.sh refactoring scripts identiques : pod disable 2022-01-28 13:25:15 +01:00
80_destroy.sh refactoring scripts identiques : pod destroy 2022-01-28 13:31:22 +01:00
90_prune.sh mutualisation scripts prune 2022-02-10 22:18:42 +01:00
ci_build-images.sh Commandes podman : invocation explicite container/image 2023-04-21 13:53:55 +02:00
docker-compose.yml Seafile : websocket 2023-06-15 22:30:05 +02:00
README.md Update README.md 2022-11-08 21:30:58 +00:00
vars.sh Seafile : websocket 2023-06-15 22:30:05 +02:00

README.md

Seafile

Première installation

soucis d'URL

À la première connexion en admin, changer les URL (https) dans l'interface d'administration.

Administrateur systeme SERVICE_URL

MAJ seafile

Modifier la version cible dans vars.sh (ici pour l'exemple : 8.0.8)

cd /opt/services-garbaye/podman-seafile
export GARBAYE_SEAFILE_MYSQL_ROOT_PASSWORD=XXXXXXXXXXXXXXXX
./40_stop.sh
./70_disable.sh
./80_destroy.sh
./10_install.sh
./20_enable.sh
./30_start.sh

Restauration

À partir d'une copie des home utilisateur (volumes podman compris) dans /backup :

  • En tant qu'utilisateur podman-seafile :
podman volume create podman-seafile_seafile-data
podman volume create podman-seafile_seafile-db
  • En tant que root :
# La restauration par "mv" nécessite une correction du contexte SELinux. Privilégier "rsync" si possible.
mv /backup/home/podman-seafile/.local/share/containers/storage/volumes/podman-seafile_seafile-data/_data/* ~podman-seafile/.local/share/containers/storage/volumes/podman-seafile_seafile-data/_data/
mv /backup/home/podman-seafile/.local/share/containers/storage/volumes/podman-seafile_seafile-db/_data/* ~podman-seafile/.local/share/containers/storage/volumes/podman-seafile_seafile-db/_data/

# le volume seafile-data est déjà root:root (ce qu'on veut). Pas besoin de chown.
chown -R podman-seafile:podman-users ~podman-seafile/.local/share/containers/storage/volumes/podman-seafile_seafile-db/_data
  • En tant qu'utilisateur podman-seafile :
podman unshare chown -R 999:999 ~/.local/share/containers/storage/volumes/podman-seafile_seafile-db/_data
chown -R podman-seafile:podman-users /home/podman-seafile/.local/share/containers/storage/volumes/podman-seafile_seafile-data/_data/logs/var-log

podman unshare chown -R 0:43 ~/.local/share/containers/storage/volumes/podman-seafile_seafile-data/_data/logs/var-log/btmp*
podman unshare chown -R 0:43 ~/.local/share/containers/storage/volumes/podman-seafile_seafile-data/_data/logs/var-log/wtmp*
podman unshare chown -R 0:43 ~/.local/share/containers/storage/volumes/podman-seafile_seafile-data/_data/logs/var-log/lastlog
podman unshare chown -R 0:4 ~/.local/share/containers/storage/volumes/podman-seafile_seafile-data/_data/logs/var-log/apt/term.log*
podman unshare chown 0:4 ~/.local/share/containers/storage/volumes/podman-seafile_seafile-data/_data/logs/var-log/nginx
podman unshare chown 33:4 ~/.local/share/containers/storage/volumes/podman-seafile_seafile-data/_data/logs/var-log/nginx/*
podman unshare restorecon -R ~/.local/share/containers/storage/volumes/podman-seafile_seafile-db/_data
podman unshare restorecon -R ~/.local/share/containers/storage/volumes/podman-seafile_seafile-data/_data
  • Exporter les variables d'environnement et procéder à l'installation normale (10_install.sh)