@girish that’s what I thought initially, but I checked both of those and was able to carry on working other prjects while waiting.
I don’t understand it, and can only put it down to a docker weirdness.
After a while I noticed that local docker desktop was asking to update, and after that I cleared the docker environment.
Then all is back to normal (whatever that is).
Phew
@robi good question, but I don’t recall, I have used rclone for access to different systems, I just didn’t recall how the cloudron was done when setting up a new machine, and didn’t pay attention to what an old connection was telling. User error, pure & simple.
I ‘m trying to use Logseq more as an accessible brain dump, discipline of taking time to log instead of rushing forwards is difficult for me (old dog, new trick).
@timconsidine You are so right. The best day for Team Cloudron is one in which there are no updates. I give @girish @nebulon @joseph an enormous amount of credit for the job they do. As someone who rolls out ~ monthly updates to users, every time that happens I pray that me and my team didn't miss something important. But it happens to all of us, despite good processes and best of intentions. But 8.3 will be replaced shortly with 8.3.1 and then 8.4 and then 9.0. And this difficult day will be replaced in everyone's memory by the great things that are yet to come!
There are threads saying that running in Terminal xattr -c /path/to/app will clear the flag.
Mixed feelings about this.
hey, why not, surely devs on Trilium are legit and it's just Apple bureaucracy
err, that's a slippery slope and the protection's are there for a purpose.
hmmm, are Trilium devs not committed enough to sign their apps properly (it's not difficult compared to the rest of their dev effort, jeez, even I have an Apple developer licence.
Going to take a timeout and just use the browser interface for now.
I've tried for a while to get a good UK based VPS as I moved away from Bytemark a while ago and haven't found anything as good. I'd love to go with Mythic Beasts but they aren't competitive. I use Hetzner right now but there was doubting voices about them on Mastodon a couple of months back when they failed to stop some abuse, not sure what was exactly going on there.
Just doing a local build of your repo (outside of Cloudron) and modifying your start.sh so that output is done to the container, it reports as running on port 8000 (on localhost, but also globally). /healtcheck does not seem to exist (gives a 404), but / gives a 200 for me. On the browser however it just loads endlessly.
Looking at the devtools on Chrome it tries to load a service worker (worker.js) which only gives a 404, but would anyways need https to function properly.
T
