Update gitea docs

Give the location of the database backups, and update the replication
section.

Change-Id: Ic687ab3bab1a1534cdd26d357f729db054e8b60e
This commit is contained in:
Ian Wienand 2019-11-15 10:21:51 +11:00
parent 7e3ad37e5a
commit 4bb7746347
1 changed files with 15 additions and 4 deletions

View File

@ -92,9 +92,13 @@ Next we stop the gitea services::
docker stop $GITEA_CONTAINER_IDS docker stop $GITEA_CONTAINER_IDS
With services stopped and the container id captured we are ready to restore With services stopped and the container id captured we are ready to
the database. We use ``docker exec`` and not ``docker-compose exec`` for restore the database. First find the database to restore; it is
performance reasons:: backed up in ``/var/backups/gitea-mariadb`` on gitea hosts. You can
copy and uncompress it.
Then restore the database (note we use ``docker exec`` and not
``docker-compose exec`` for performance reasons)::
docker exec -i $DB_CONTAINER_ID bash -c '/usr/bin/mysql -uroot -p"$MYSQL_ROOT_PASSWORD"' < /root/gitea-mariadb.sql docker exec -i $DB_CONTAINER_ID bash -c '/usr/bin/mysql -uroot -p"$MYSQL_ROOT_PASSWORD"' < /root/gitea-mariadb.sql
@ -128,4 +132,11 @@ ecdsa key)::
Then we can ask Gerrit to replicate all repo content into our new empty repos:: Then we can ask Gerrit to replicate all repo content into our new empty repos::
ssh -p 29418 $USER@review.opendev.org replication start --url giteaXY.opendev.org ssh -p 29418 $USER@review.opendev.org gerrit replication start --url giteaXY.opendev.org
You can monitor the progress of this with::
ssh -p 29418 $USER@review.opendev.org gerrit show-queue
Once this is complete, add the server back into the haproxy as
discussed above.