Implement dev version

This is the default build for branches.

.github/workflows/docker-image.yaml

@@ -54,7 +54,7 @@ jobs:
             echo "CONFIG_FILE=Omada Stable/config.yaml" >> $GITHUB_ENV
           else
             echo "IMAGE_NAME=${{ secrets.DOCKER_USER_NAME }}/home-assistant-omada-dev" >> $GITHUB_ENV
-            echo "CONFIG_FILE=Omada Beta/config.yaml" >> $GITHUB_ENV
+            echo "CONFIG_FILE=Omada Dev/config.yaml" >> $GITHUB_ENV
           fi
 
       - name: Set INSTALL_VER from config.yaml

Omada Dev/config.yaml

@@ -0,0 +1,40 @@
+---
+name: Omada Controller Dev
+image: jeruntu/home-assistant-omada-dev
+version: beta-5.15.6.4
+slug: omada_controller_dev
+description: TP-Link Omada Controller software
+webui: https://[HOST]:[PORT:8043]
+startup: application
+arch:
+  - aarch64
+  - amd64
+init: false
+url: https://github.com/jkunczik/home-assistant-omada
+map:
+  - ssl
+options:
+  enable_hass_ssl: false
+  certfile: /ssl/fullchain.pem
+  keyfile: /ssl/privkey.pem
+schema:
+  enable_hass_ssl: bool
+  certfile: str
+  keyfile: str
+ports:
+  8088/tcp: 8088
+  8043/tcp: 8043
+  8843/tcp: 8843
+  29810/tcp: 29810
+  29810/udp: 29810
+  29811/tcp: 29811
+  29811/udp: 29811
+  29812/tcp: 29812
+  29812/udp: 29812
+  29813/tcp: 29813
+  29813/udp: 29813
+  29814/tcp: 29814
+  29815/tcp: 29815
+  29815/udp: 29815
+  29816/tcp: 29816
+  29816/udp: 29816

README.md

@@ -31,15 +31,16 @@ Set `Enable Home Assistant SSL` to `true`, and enter the full path for:
 - `Certificate file`
 - `Private key`
 
-The default paths are compatible with the `LetsEncrypt` Add-On.
+The default paths are compatible with the `Letsencrypt` Add-On.
 
 ## Release a new version
 
 To update the controller to a new version, the following steps have to be done:
 
 1. Upgrade the mbentley submodule to the latest on `master`.
-2. Upgrade the version in `config.yaml` in either beta or stable.
-This version should match exactly with one for the versions listed [here](https://github.com/mbentley/docker-omada-controller-url/blob/master/omada_ver_to_url.sh).
+2. Upgrade the version in `config.yaml` first in dev.
+Than upgrade either beta or stable for the release.
+This version should match exactly with one of the versions listed [here](https://github.com/mbentley/docker-omada-controller-url/blob/master/omada_ver_to_url.sh).
 3. If everything is working as expected, you can create a new GitHub release.
 The tag should match the version in the config.yaml exactly.
 Otherwise the pipeline will fail.