From 1daf44b6e185a597d9ddc6f615e36732ba84d8ee Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Tue, 17 Sep 2024 16:38:39 +0000 Subject: [PATCH] README.md: Update Versions --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 041886a..cfcc3d2 100644 --- a/README.md +++ b/README.md @@ -14,17 +14,17 @@ Updated version, only with Version tags - NodeJS 20 - Alexa-Fhem 0.5.64 - docker pull ghcr.io/fhem/alexa-fhem:5.0.12 + docker pull ghcr.io/fhem/alexa-fhem:5.0.13 #### To start your container right away: -docker run -d --name alexa-fhem ghcr.io/fhem/alexa-fhem:5.0.12 +docker run -d --name alexa-fhem ghcr.io/fhem/alexa-fhem:5.0.13 ### Permanent storage Usually you want to keep your FHEM setup after a container was destroyed (or re-build) so it is a good idea to provide an external directory on your Docker host to keep that data: - docker run -d --name alexa-fhem -v /some/host/directory:/alexa-fhem ghcr.io/fhem/alexa-fhem:5.0.12 + docker run -d --name alexa-fhem -v /some/host/directory:/alexa-fhem ghcr.io/fhem/alexa-fhem:5.0.13 #### Verify if container is runnung After starting your container, you may check the web server availability: @@ -46,7 +46,7 @@ You can use one of those variants by adding them to the docker image name like t docker pull ghcr.io/fhem/alexa-fhem:latest docker pull ghcr.io/fhem/alexa-fhem:5 - docker pull ghcr.io/fhem/alexa-fhem:5.0.12 + docker pull ghcr.io/fhem/alexa-fhem:5.0.13 If you do not specify any variant, `latest` will always be the default. @@ -125,7 +125,7 @@ services: # Minimum example w/o any custom environment variables of alexa-fhem container alexa-fhem: - image: ghcr.io/fhem/alexa-fhem:5.0.12 + image: ghcr.io/fhem/alexa-fhem:5.0.13 restart: always networks: - fhem_net