* Automatic Dockerfile update by release process

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

.github/workflows/no-response.yml

@@ -1,25 +0,0 @@
-name: No Response
-
-# Both `issue_comment` and `scheduled` event types are required for this Action
-# to work properly.
-on:
-  issue_comment:
-    types: [created]
-  schedule:
-    # Schedule for five minutes after the hour, every hour
-    - cron: '5 3 * * *'
-
-jobs:
-  noResponse:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: lee-dohm/no-response@v0.5.0
-        with:
-          token: ${{ github.token }}
-          # Number of days of inactivity before an Issue is closed for lack of response
-          daysUntilClose: 90
-          # Label requiring a response
-          responseRequiredLabel: waiting-for-user
-          # Comment to post when closing an Issue for lack of response. Set to `false` to disable
-          closeComment: >
-            Closing: more than 90 days without user response. Feel free to reopen with your comments.

Dockerfile

@@ -5,7 +5,7 @@ ARG SRCIMAGE=debian:bullseye-slim
 
 FROM  $SRCIMAGE AS builder
 
-ARG LSMB_VERSION="1.10.21"
+ARG LSMB_VERSION="1.9.26"
 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.21"
+ARG LSMB_VERSION="1.9.26"
 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

@@ -14,9 +14,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
+through the ledgersmb-dev-docker project. See https://github.com/ledgersmb/ledgersmb-dev-docker/blob/master/README.md#getting-started.
-container's README](https://github.com/ledgersmb/ledgersmb-dev-docker/blob/master/README.md#getting-started)
-for more information.
 
 # What is LedgerSMB?
 
@@ -51,11 +49,11 @@ or manually with docker only.
 
 ## Docker-Compose: Installation and start
 
-This repository provides a file named `docker-compose.yml` which can be used to
+This image provides `docker-compose.yml` which can be used to pull related
-pull related images, install them, establish an internal network for their
+images, install them, establish an internal network for their communications,
-communications, adjust environment variables, start and stop LedgerSMB. The
+adjust environment variables, start and stop LedgerSMB. The only instructions
-only instructions required, after the optional edition of the file to adjust
+required, after the optional edition of the file to adjust the environment
-the environment variables, are:
+variables, are:
 
 ```plain
  $ docker-compose pull
@@ -110,7 +108,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 +173,13 @@ yet with the deprecation, the abilities have expanded.
 
 The following parameters are now supported to set mail preferences:
 
-* `LSMB_MAIL_SMTPHOST` \
+* `LSMB_MAIL_SMTPHOST`
-  The host name/IP-address of the SMTP server that will forward mail from
+* `LSMB_MAIL_SMTPPORT`
-  LedgerSMB to the outside world.
+* `LSMB_MAIL_SMTPTLS`
-* `LSMB_MAIL_SMTPPORT` \
+* `LSMB_MAIL_SMTPSENDER_HOSTNAME`
-  The port that the SMTP server in `LSMB_MAIL_SMTPHOST` listens to.
+* `LSMB_MAIL_SMTPUSER`
-* `LSMB_MAIL_SMTPTLS` \
+* `LSMB_MAIL_SMTPPASS`
-  Can be one of `no` (default), `yes` or `raw`. `yes` indicates to use
+* `LSMB_MAIL_SMTPAUTHMECH`
-  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.
 
 # 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