Martin
Martin
that's really weird, are you running the frontend in docker after starting start_services.sh ? are there any error in docker compose log ?
searxng is not required for the frontend. can you update the repository (clone again), delete the frontend container in docker and build again (./start_services.sh)
Hello could you submit a pull request with your fix that refer this issue (please submit it as draft for now)
sure! what tests would you like to add ? Feel free to do pull request
will look into it
done, full docker contairization as been merged as well so it's only an options for those who still which to run backend on host
Hey, really nice maybe you could set the pull request as "Draft". It won't be merged yet because: - As you say I don't think people would appreciate that we...
You mean on discord? yeah we don't have an active contributor base at the moment haha so I was the only one replying. Can you confirm you are still on...
Hello, should be fixed by #403
It is indeed a permission issue that you fix with `sudo usermod -aG docker $USER` as clrblind said.