Open pmbrandvold opened 1 month ago
Same here. Is there any solution?
What would be easier is if I could just use the tracksapp/tracks image, but there's no documentation on how to set that up in a compose stack. It seems as though it requires a database, which makes sense. But there's no documentation on how to set a database up to be used with the tracksapp/tracks image (which is presumably just a frontend? I'm not sure). When I just pull "tracksapp/tracks" and run it, I get an error that seems to be from no user existing yet, but there's no instructions on how to set up a user.
I was able to get the script/setup and script/server files to run after changing every reference to "docker-compose" to "docker compose" to reflect how the docker engine calls compose now. However, this resulted in an instance that runs but doesn't have a users table, apparently. After hitting localhost:3000 I can launch a login page that says "We're sorry, but something went wrong. If you are the application owner check the logs for more information."
The container logs show:
It's clear there is' a missing table (tracks.users) but as far as the instructions say, things should be working after running the scripts.
Beyond this issue, there's no really effective way for me to run this in something like portainer, because it requires me to run a bunch of separate scripts to manipulate the docker file and container instances. Is there an easier way to do this? I have an old version of tracks working but it's using Stannoe's docker image which is outdated. Ultimately I just want to update my current instance but I'm stuck until I have a way to set things up with the latest code...