ssickle

There is a problem with InfluxDB's template: if someone who's been using this template for a long time hits update in the UI, it'll update the container to 2.3 and potentially cause data loss. Ideally I would like to direct these legacy users to my InfluxDB1 template. See conversation here where the author says I can take over. I considered the following: Removing template via PR on original author repo (afraid this may break some users) Checking the moderation.json (only saw depreciating an entire container there) Creating InfluxDB2 and InfluxDB1 templates and letting user (different name and tags used, shouldn't show as a dupe luckily) @Squid could you shed some light on how CA would like to best support this scenario? I don't see a Depreciated tag or anything like that.

Hey there! The way I got this working originally was to point the "java server" variable to my unraid box's IP, using the minecraft server template from ich777. I later found a better way (in my opinion) to do this, using spigot you can add the GeyserMC jar right to the mods and the server itself will support it without an additional container like this.

GeyserMC is a translation layer to allow bedrock and java edition players to come together on the same server and have fun. Big thanks to nefald for getting this docker container ready - I only made the template for it to run from community apps! Check out the projects git for latest changes and support related to the docker image. For template related issues, please contact me here!

Weatherflow2mqtt is a template based around the work of briis/hass-weatherflow2mqtt. You will want to use mosquitto or another MQTT broker.