Will try this, thanks for the tip

Thanks, good point. Didn’t know about that risk

This already had a brim but it is quite ugly. The thing is I had the same failure while printing a bigger object like a Stormtrooper helmet. Randomly popped off the bed after like 2.5 hours

I have cleaned the bed already with alcohol and microfiber cloth. Yeah the brim is supposed to be cylindrical but it obviously isn’t :D . Is that a modification I should do in Prusa Slicer? For the first layer height

It’s pretty much a “develop from zero” situation. You can import assets, but will probably have to at least fix them up. If you are lucky, the two engines use the same language, but probably not. For example Unity uses C# while UE5 uses C++. And then you didn’t even get to the parts where you actually use use the engine. Everything that touches the capabilities of the specific game engine need to be rewritten. That is off the top of my head: interaction, physics engine usage, collision engine usage, AI stuff etc.

Here is what I’m using atm. Is there a better way to do this? I’m still learning K8S :)

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: sonarr-pvc
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: longhorn
  resources:
    requests:
      storage: 250Mi
---
[....]
volumes:
      - name: config
        persistentVolumeClaim:
          claimName: sonarr-pvc

Yeah I’m using Longhorn. Might be that I have set it up wrong, but didn’t seem to have helped with the DB corruption issue.

Basically this. I have my home stuff running in a K3S cluster, and I had to restore my Sonarr volume several times because the SQLite DB has corrupted. Transitioning to Postgres should solve this issue, and I already have quite a few other stuff in it, for example Radarr and Prowlarr

I got the same Obsidian+Syncthing setup atm, just haven’t really tried to use it for writing yet. Wanted to see what else others use that may trump it :)

No error logs, based on the logs tho it just ignores the config and uses the filesystem. So predictably once my small config mount fills up (this was before emptyDir), it starts to error out saying no more space on disk. Seemingly this didn’t cause any errors for Lemmy, still it doesn’t feel right :)

Yeah, just after posting this I saw a different comment in another post linking to those tickets :D Of course I would find my question answered 5 minutes after posting it. Thanks anyway :)