Wiki » History » Version 4
Dominik Meyer, 12/22/2024 04:09 PM
| 1 | 1 | Dominik Meyer | # FHEM Container Image |
|---|---|---|---|
| 2 | |||
| 3 | This projects aims at creating a secure container for running the Home-Automation System [FHEM](https://fhem.de/). |
||
| 4 | It is **not** intended for running in a *docker* environment but in a *kubernetes* environment. |
||
| 5 | 2 | Dominik Meyer | |
| 6 | 4 | Dominik Meyer | ## Usage Strategy |
| 7 | |||
| 8 | The main usage strategy of this container is using external protocols like MQTT or HTTP to update the devices |
||
| 9 | within FHEM. All the modules of a normal FHEM installation are available but I will **not** provide any support |
||
| 10 | in setting them up in a containerized environment. |
||
| 11 | |||
| 12 | 2 | Dominik Meyer | ## Features |
| 13 | |||
| 14 | ### FHEM Main branch |
||
| 15 | 3 | Dominik Meyer | |
| 16 | The main branch of FHEM is still called *master* but I consider that inappropriate so I will use **main** instead. |
||
| 17 | On every build the container will fetch the current main branch of FHEM and updates the container image with it. |
||
| 18 | 1 | Dominik Meyer | |
| 19 | 4 | Dominik Meyer | ### Update Strategy |
| 20 | 3 | Dominik Meyer | |
| 21 | This image does not support updating FHEM or the underlying Debian image by executing any command. Updates will **only** |
||
| 22 | be distributed through updated container images. This is the established way of kubernetes and will **never** been changed |
||
| 23 | by myself. |
||
| 24 | 2 | Dominik Meyer | |
| 25 | 1 | Dominik Meyer | ### Additional FHEM Modules |
| 26 | 4 | Dominik Meyer | Because you cannot add FHEM update sites at runtime of the container the image includes some modules I need. |
| 27 | |||
| 28 | #### FHEM-NTFY |
||
| 29 | |||
| 30 | #### SST |
||
| 31 | |||
| 32 |