Update README.md -- 1.10 is EOL

This dependency causes the lsmbdata volume to be forcibly created from the lsmb container
which means that the correct assets will be copied in.

Dockerfile

@@ -5,7 +5,7 @@ ARG SRCIMAGE=debian:bullseye-slim
 
 FROM  $SRCIMAGE AS builder
 
-ARG LSMB_VERSION="1.10.17"
+ARG LSMB_VERSION="1.9.30"
 ARG LSMB_DL_DIR="Releases"
 ARG ARTIFACT_LOCATION="https://download.ledgersmb.org/f/$LSMB_DL_DIR/$LSMB_VERSION/ledgersmb-$LSMB_VERSION.tar.gz"
 
@@ -51,7 +51,7 @@ LABEL org.opencontainers.image.description="LedgerSMB is a full featured double-
  the LedgerSMB project is to bring high quality ERP and accounting capabilities\
  to Small and Midsize Businesses."
 
-ARG LSMB_VERSION="1.10.17"
+ARG LSMB_VERSION="1.9.30"
 ARG LSMB_DL_DIR="Releases"
 ARG ARTIFACT_LOCATION="https://download.ledgersmb.org/f/$LSMB_DL_DIR/$LSMB_VERSION/ledgersmb-$LSMB_VERSION.tar.gz"
 

README.md

@@ -4,8 +4,9 @@ Dockerfile for LedgerSMB Docker image
 
 # Supported tags
 
-- `1.10`, `1.10.x`, `latest` - Latest official release from the 1.10 branch
-- `1.9`, `1.9.x` - Latest official release from the 1.9 branch
+- `1.11`, `1.11.x`, `latest` - Latest official release from the 1.11 branch
+- `1.10`, `1.10.38` - Last official release from the 1.10 branch (End-of-Life)
+- `1.9`, `1.9.30` - Last official release from 1.9 branch (End-of-Life)
 - `1.8`, `1.8.31` - Last official release from the 1.8 branch (End-of-Life)
 - `1.7`, `1.7.41` - Last official release from the 1.7 branch (End-of-Life)
 - `1.6`, `1.6.33` - Last official release from the 1.6 branch (End-of-Life)
@@ -14,9 +15,7 @@ Dockerfile for LedgerSMB Docker image
 - `master` - Master branch from git, unstable
 
 Containers supporting the development process are provided
-through the ledgersmb-dev-docker project. See [the development
-container's README](https://github.com/ledgersmb/ledgersmb-dev-docker/blob/master/README.md#getting-started)
-for more information.
+through the ledgersmb-dev-docker project. See https://github.com/ledgersmb/ledgersmb-dev-docker/blob/master/README.md#getting-started.
 
 # What is LedgerSMB?
 
@@ -51,11 +50,11 @@ or manually with docker only.
 
 ## Docker-Compose: Installation and start
 
-This image provides a file named `docker-compose.yml` which can be used to
-pull related images, install them, establish an internal network for their
-communications, adjust environment variables, start and stop LedgerSMB. The
-only instructions required, after the optional edition of the file to adjust
-the environment variables, are:
+This image provides `docker-compose.yml` which can be used to pull related
+images, install them, establish an internal network for their communications,
+adjust environment variables, start and stop LedgerSMB. The only instructions
+required, after the optional edition of the file to adjust the environment
+variables, are:
 
 ```plain
  $ docker-compose pull
@@ -110,7 +109,7 @@ like `POSTGRES_HOST` above.
 
 # Set up LedgerSMB
 
- * Visit http://myledger:5762/setup.pl.
+ * Visit http://localhost:5762/setup.pl.
  * Log in with the "postgres" user and the password `abc` as given above -
    or with the credentials of your own database server in case of a manual
    setup - and provide the name of a company (= database name) you want to
@@ -175,30 +174,13 @@ yet with the deprecation, the abilities have expanded.
 
 The following parameters are now supported to set mail preferences:
 
-* `LSMB_MAIL_SMTPHOST` \
-  The host name/IP-address of the SMTP server that will forward mail from
-  LedgerSMB to the outside world.
-* `LSMB_MAIL_SMTPPORT` \
-  The port that the SMTP server in `LSMB_MAIL_SMTPHOST` listens to.
-* `LSMB_MAIL_SMTPTLS` \
-  Can be one of `no` (default), `yes` or `raw`. `yes` indicates to use
-  STARTTLS over a regular SMTP connection; `raw`' indicates an SMTP connection
-  should be established over a TLS connection (a.k.a. smtps).
-* `LSMB_MAIL_SMTPSENDER_HOSTNAME` (optional) \
-  When set, used to identify the host when connecting to an SMTP server. When
-  not set, the host is queried for its host name.
-* `LSMB_MAIL_SMTPUSER` \
-  Username to authenticate to the SMTP host in `LSMB_MAIL_SMTPHOST`.
-* `LSMB_MAIL_SMTPPASS` \
-  Password to authenticate to the SMTP host in `LSMB_MAIL_SMTPHOST` with the
-  user in `LSMB_MAIL_SMTPUSER`.
-* `LSMB_MAIL_SMTPAUTHMECH` \
-  A space separated list of SASL mechanisms to be used for authentication of
-  the smtp connection with the SMTP server. Available mechanisms depend on
-  your installed environment, but the following mechanisms should be available
-  in all of them: `PLAIN` `LOGIN` `CRAM_MD5` & `DIGEST_MD5`. **Note that**
-  `PLAIN` or `LOGIN` send passwords in plain text over the wire to the SMTP
-  server; only use these methods in combination with TLS encryption.
+* `LSMB_MAIL_SMTPHOST`
+* `LSMB_MAIL_SMTPPORT`
+* `LSMB_MAIL_SMTPTLS`
+* `LSMB_MAIL_SMTPSENDER_HOSTNAME`
+* `LSMB_MAIL_SMTPUSER`
+* `LSMB_MAIL_SMTPPASS`
+* `LSMB_MAIL_SMTPAUTHMECH`
 
 # Advanced setup
 

docker-compose-reverseproxy.yml

@@ -25,9 +25,6 @@ services:
       - "./nginx.conf:/etc/nginx/nginx.conf"
     ports:
       - "8080:8080"
-    # Comment the line below to stop the container from restarting on boot
-    # unless it was manually stopped
-    restart: unless-stopped
   lsmb:
     volumes:
       - "lsmbdata:/srv/ledgersmb"

docker-compose.yml

@@ -25,13 +25,10 @@ services:
       - internal
     volumes:
       - "pgdata:/var/lib/postgresql/data"
-    # Comment the line below to stop the container from restarting on boot
-    # unless it was manually stopped
-    restart: unless-stopped
   lsmb:
     depends_on:
       - postgres
-    image: ghcr.io/ledgersmb/ledgersmb:1.10
+    image: ghcr.io/ledgersmb/ledgersmb:1.9
     networks:
       - internal
       - default
@@ -70,9 +67,6 @@ services:
       # hosted in a separate container, this setting needs to be adjusted.
       #
       # PROXY_IP: 172.17.0.1/12
-    # Comment the line below to stop the container from restarting on boot
-    # unless it was manually stopped
-    restart: unless-stopped
 
 # having the dbdata volume is required to persist our
 # data between PostgreSQL container updates; without