MatthK
MatthK
I just pulled the latest image from `docker pull docker.umami.is/umami-software/umami:mysql-latest`. Removed the container, and started it again. The log file looks fine, and even did a migration. ``` yarn run...
And I just checked the console again after trying V. 1.37.0 again: On the main page I get this: ``` main-f1f37299d5d02885.js:1 Error: Abort fetching component for route: "/" at main-f1f37299d5d02885.js:1:54019...
So there's no solution to this?
Would that work? - Git clone into a new directory - Change all the texts in the files to the desired language - Make a link to the "real" db.sqlite3...
Hmm, strange enough. I tried on an iPhone and Android phone, with various different browsers, from Safari, Firefox, Edge Chrome. It's not that dramatic.
I think I used the `docker cp foo.txt mycontainer:/foo.txt` to copy my own logo into the container. The path should be at `mycontainer:/usr/local/searx/searx/static/themes//img/`
As I just updated my docker container to the latest build to get rid of the google bug, I can confirm the following updated my logo: `sudo docker cp ~/searx/logo_searx_a.png...
My wife just moved back to the Mainland temporarily and we couldn't communicate using Signal anymore. I first tried to install the TLS-Proxy but that didn't work. A OpenVPN connection...
It seems my optimism was a bit too early. The VPN now seems to be no longer working. When doing a DNS Leak Test, my wife gets various IP addresses,...
"I don't think this is supposed to be a user support ticket system." OK, point taken.