Hi, ingress is super hard to implement and the biggest issue is that Mealie requires a hardcoded url at container creation which is not compatible with the way ingress works.
Should be good now - I’ll keep on v2.0 from now on. But make a full HA backup just to be sure! The database from your version is located in the /config of homeassistant, which is not backuped when doing the add-on back-up.
Once the Mealie mess is sorted and people have safely migrated to the new version, I’m implement the new logic for config storage that will allow to have it backuped with the addon
Hi, here is the initial thread discussing the lack of support for subpaths as ingress needs: Alexbelgium repo : 90+ addons - #332 by kenobrandt. BTW, several official add-ons also don’t support ingress (like bitwarden) in the end it is quite a hack…
If you find a way though I’ll be more than happy to implement it
Hi, honestly I have already way too many addons and prefer focusing on maintenance, except for things that I would myself use and especially given there is already strong addons for reverse proxies such as Nginx supported by HA itself. However you could use the portainer addon to run it