bilogic

 Ok, I stopped JF and did what you said and got the above using VSCode's terminal After JF restarted, `transcodes` became a symlink, but `metadata` stayed as-is

what do you mean by `ingress`?

If you use HTTP, ingress works, but if configured for HTTPS, ingress stops working. I switch to using caddy to provide HTTPS when accessing jellyfin directly, so it works both...

Using caddy also cuts down on the need to to deal with the quirks of each addon individually, e.g. Navidrome needs the cert in PFX format... 🤦‍♂

@nordeep 1. I thought that `metadata` is automatically created by JF and acts like a cache? 2. How are you adding custom data to it? 3. From what I observe,...

let me run thru the tutorials thanks

I'm basing this off the gitea add-on as my base, but I keep getting this error when trying to install my new add-on 

Yes, I'm aware it was due to the `ADD --chmod`, but why does it work for gitea and not mine? What I can't understand is: 1. I'm replicating the `Dockerfile`...

I found out was it was due to `"image": "ghcr.io/alexbelgium/gitea-{arch}",` in `config.json`

https://github.com/bilogic/ha-addons/tree/470a1edfea1b1fc5d813560357e9f95173276a71/navidrome It appears that a `Docker` file is not absolutely required, but I do need some way to change the ENV values.