Docker with Gitea

hit log

If you encounter a problem, look at the log first! ! !

Gitea’s log and Debug

There are 4 ways for Gitea’s log output:

• https://docs.gitea.io/en-us/logging-configuration/#log-outputs

Gitea Debug

• https://docs.gitea.io/en-us/logging-configuration/#debugging-problems

1. Enable console output log
2. Modify log level

Data Migration, Backup, Recovery

• https://docs.gitea.io/en-us/backup-and-restore/#using-docker-restore

other question one

The main performance is that when INSTALL_LOCK = true , it cannot be started, and the version field of the version table has no value.

As for why this field is missing when restoring data, this may be caused by using a lower version of gitea and exporting data with gitea dump , because this problem may exist in versions 1.15-dev and below (1.15-dev verification the problem exists).

The solution is to add a version field to the version table and set the value of the version field to the corresponding version number.

Solution 1: Before importing data, modify the SQL statement to create the version table in the gitea-db.sql file.

Please modify the following SQL statements to suit your needs

 CREATE TABLE IF NOT EXISTS `version` (`id` BIGINT(20) PRIMARY KEY AUTO_INCREMENT NOT NULL, `version` BIGINT(20) NOT NULL) DEFAULT CHARSET utf8mb4 ROW_FORMAT=DYNAMIC;INSERT INTO `version` (`id`, `version`) VALUES (1, 178);

Option 2: After importing the data, add the version field to the Version table and set the corresponding value.

refer to:

• https://github.com/go-gitea/gitea/issues/15678

This article is reprinted from https://www.wujingquan.com/posts/331d3824.html
This site is for inclusion only, and the copyright belongs to the original author.