Upgrade Plume + debug info

This commit is contained in:
Quentin 2022-04-23 22:04:14 +02:00
parent 2695a79e8a
commit 60ad398c44
Signed by: quentin
GPG key ID: E9602264D639FF68
4 changed files with 29 additions and 9 deletions

View file

@ -82,8 +82,8 @@ services:
build:
context: ./plume/build/plume
args:
VERSION: 57a54cf016cdf566fe45c081bda1971f176c4532
image: superboum/plume:v7
VERSION: 8709f6cf9f8ff7e3c5ee7ea699ee7c778e92fefc
image: superboum/plume:v8
postfix:
build:
@ -106,7 +106,3 @@ services:
context: ./backup/build/backup-consul
image: lxpz/backup_consul:12
backup-matrix:
build:
context: ./backup/build/backup-matrix
image: superboum/backup_matrix:4

View file

@ -29,4 +29,4 @@ LDAP_USER_MAIL_ATTR=mail
LDAP_TLS=false
RUST_BACKTRACE=1
RUST_LOG=info
RUST_LOG=trace

View file

@ -23,7 +23,7 @@ job "plume-blog" {
driver = "docker"
config {
image = "superboum/plume:v7"
image = "superboum/plume:v8"
network_mode = "host"
ports = [ "web_port" ]
#command = "cat"

View file

@ -17,4 +17,28 @@ plm users new \
```
That's all folks, now you can use your new account at https://plume.deuxfleurs.fr
## Bug and debug
If you can't follow a new user and have this error:
```
2022-04-23T19:26:12.639285Z WARN plume::routes::errors: Db(DatabaseError(UniqueViolation, "duplicate key value violates unique constraint \"follows_unique_ap_url\""))
```
You might have an empty field in your database:
```
plume=> select * from follows where ap_url='';
id | follower_id | following_id | ap_url
------+-------------+--------------+--------
2118 | 20 | 238 |
(1 row)
```
Simply set the `ap_url` as follows:
```
plume=> update follows set ap_url='https://plume.deuxfleurs.fr/follows/2118' where id=2118;
UPDATE 1
```