documented fixes

master
root 1 year ago
parent 8bf73e508f
commit 12f5f682d1
  1. 30
      Migration.md
  2. 1
      migrate.sh
  3. 5
      modules/gitea.nix

@ -23,3 +23,33 @@ cd
export GITEA_WORK_DIR=/var/lib/gitea
/nix/store/*-gitea-1.15.2/bin/gitea doctor --all
```
#### Fix problems caused by database schema changes between Gitea 1.8.3 and 1.15.2
2 Factor Auth didn't work, but was only used by 2 users anyway. We delete the old settings:
```sql
delete from two_factor;
```
There is a new column `repository.owner_name` that needs be set. Otherwise the web frontend displayed links starting with `//`.
Before fixing, we checked the `owner_names` queried by joining via `"user".id = repo.owner_id`:
```sql
select "user".lower_name, repo.owner_name, repo.lower_name from repository as repo inner join "user" on "user".id = repo.owner_id;
```
```sql
UPDATE repository
SET owner_name = map.name
FROM (SELECT "user".lower_name AS name, repository.owner_id AS id
FROM repository INNER JOIN "user" ON "user".id = repository.owner_id
) AS map
WHERE map.id = repository.owner_id;
```
#### Problems with old logins
Till now `PASSWORD_HASH_ALGO` `argon2` was used, but seems not to work in the new version.
Using the password recovery works.

@ -6,6 +6,7 @@ DATABASE=gitea
cd /tmp/
unzip ${DUMP}.zip
unzip gitea-repo.zip
systemctl stop gitea

@ -40,6 +40,11 @@
HOST = "mail.c3d2.de:465";
IS_TLS_ENABLED = true;
};
service = {
NO_REPLY_ADDRESS = "no_reply@c3d2.de";
REGISTER_EMAIL_CONFIRM = true;
ENABLE_NOTIFY_MAIL = true;
};
};
};