Describe the bug
Taskcafe-web doesn't seem to handle database host values anymore.
Even following this guide's installation process doesn't work anymore: https://www.llewellynhughes.co.uk/post/installing-taskcafe/#install-taskcafe
Using the exact unmodified docker-compose.yml file in that guide also triggers this issue for me.
Expected behavior
I expected taskcafe-web to try and connect to taskcafe_db (the hostname) but instead it calls for 127.0.0.1 (localhost)
Screenshots / Live demo link
The taskcafe-web logs
The docker-compose.yml in use
Additional context
There is a possibility that taskcafe now expects the database to be ran on localhost but i can't seem to find any reasoning or explanation anywhere about this, the docker-compose files aren't even updated for this, so it's most likely a bug.
Describe the bug
Taskcafe-web doesn't seem to handle database host values anymore.
Even following this guide's installation process doesn't work anymore: https://www.llewellynhughes.co.uk/post/installing-taskcafe/#install-taskcafe
Using the exact unmodified docker-compose.yml file in that guide also triggers this issue for me.
Expected behavior
I expected taskcafe-web to try and connect to taskcafe_db (the hostname) but instead it calls for 127.0.0.1 (localhost)
Screenshots / Live demo link
The taskcafe-web logs
The docker-compose.yml in use
Additional context
There is a possibility that taskcafe now expects the database to be ran on localhost but i can't seem to find any reasoning or explanation anywhere about this, the docker-compose files aren't even updated for this, so it's most likely a bug.