Open Extarys opened 2 years ago
Hi, sorry for the delay, I haven't tried reproducing since I use MySQL. Does it still occur on the latest version ?
Hi! No worries I also didn't have the patience or the time to test :smile: I restarted from the beginning. I uses DB_* environment variable in my docker compose. It does seem to create some tables, or is it when I run the initial artisan command, I'm not sure but still.
When I run php artisan koel:init --no-assets
:
From koel docker I get:
Migrating database
Oops! Koel installation or upgrade didn't finish successfully.
Please try again, or visit https://docs.koel.dev for manual installation.
š„ Sorry for this. You deserve better.
From postgres I get:
Connection matched pg_hba.conf line 99: "host all all all md5"
2022-01-09 20:14:18.078 UTC [90] ERROR: cannot drop index artists_name_unique because constraint artists_name_unique on table artists requires it
2022-01-09 20:14:18.078 UTC [90] HINT: You can drop constraint artists_name_unique on table artists instead.
2022-01-09 20:14:18.078 UTC [90] STATEMENT: drop index "artists_name_unique"
2022-01-09 20:14:18.080 UTC [90] ERROR: current transaction is aborted, commands ignored until end of transaction block
2022-01-09 20:14:18.080 UTC [90] STATEMENT: DEALLOCATE pdo_stmt_00000058
Maybe my previous mistake was that I tried to connect without seeing that error above, therefore login attemps might return code 500.
Between every try, I do:
DROP DATABASE koel;
CREATE DATABASE koel;
GRANT CONNECT ON DATABASE koel TO koel;
As for the settings, I use host postgres
with port 5432
user and db koel
and it's password.
Koel image: ID: ba74268b845d64bdc0acee5e8955dceaeffb6eddf824f7012f9cf400958dc6cd Date: 2021-12-30 23:04:16 Arch: arm64
I use Postgres version 12. Everything is managed inside Portainer.
Might be the same issue as https://github.com/koel/koel/issues/1401
just
docker exec -it koel_koel_1 bash
chown -R www-data:www-data
exit
and
docker exec --user www-data -it koel_koel_1 bash
php artisan koel:init --no-assets
docker exec -it koel_koel_1 bash chown -R www-data:www-data exit
Isn't there a missing argument for the 'chown' call ?
After installation I ssh inside the container and ran
php artisan koel:init --no-assets
which created a bunch of tables inside the database. I can see the default admin user inside theusers
table,personal_access_tokens
table is empty.When I try to log in I get error 500 and this is the log:
It looks like it cannot create the token or something - although the error is different maybe it is related somehow to #54 ? Since artisan was able to create the tables I doubt it's a read/write permission issue, but to be safe I make the koel user a superuser.
I'm using Postgresql on a Pi 4. This pulled the latest docker version - not sure which one. If you need more info please ask.