LedgerSMB
The foundation for your business
Fork me on GitHub
[ledgersmb-devel] Re: Dear team i installed ledgerSMB via debian and got version 1.6.33
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ledgersmb-devel] Re: Dear team i installed ledgerSMB via debian and got version 1.6.33



Hi Harald,

If you use the old version, as you wrote in the SUBJECT, I recommend to not use it.

Instead, you should use the latest docker version, as that will work on any docker compatible system, debian, ubuntu, etc.
Installing via a traditional way could needs more experiences until you got everything working.
I also switched to docker and frankly, the developers did excellent job on this


Please refer to this, sent by the developers on Sunday:

For installation instructions and system requirements, see
   https://github.com/ledgersmb/LedgerSMB/blob/1.12.6/README.md

The release can be downloaded from our download site at
   https://download.ledgersmb.org/f/Releases/1.12.6

The release can be downloaded from GitHub at
   https://github.com/ledgersmb/LedgerSMB/releases/tag/1.12.6

Or pulled from the GitHub Container Registry
   $ docker pull ghcr.io/ledgersmb/ledgersmb:1.12.6

Or pulled from Docker Hub using the command
   $ docker pull ledgersmb/ledgersmb:1.12.6

These are the sha256 checksums of the uploaded files:

1f876d9d97932458d668ff4f5307ebc2f87d7be27a830bbd793be33b5bccd847  ledgersmb-1.12.6.tar.gz
8a9f4fa107f2332c9192a9196b76819b966ba7cc7feda4d527f9b2e237819d23  ledgersmb-1.12.6.tar.gz.asc

My docker compose file is the following for reference:

--------------------  >8  ------------------------

# This docker-compose file creates one
# compose 'project' consisting of two containers
#
#  1. The PostgreSQL data  container
#  2. The LedgerSMB application container
#
# LedgerSMB persists all its data in the database,
# so no special care needs to be taken on
# container upgrades.  With PostgreSQL, data is
# persisted across upgrades by the use of a
# special 'dbdata' volume

version: "3.2"
services:
  # Note that the container needs to be named "postgres" here,
  # because that allows us to use the default hostname ("postgres")
  # from the LedgerSMB configuration
  postgres:
    image: postgres:15-alpine
    environment:
      # Replace the password below for a secure setup
      POSTGRES_PASSWORD: CHANGEME
      PGDATA: /var/lib/postgresql/data/pgdata
    networks:
      - internal
    ports:
      - "5763:5432"
    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.12.2
      # In order to store the configuration outside the image, allowing it to
      # be edited between container restarts, uncomment the section below and
      # change the 'source' to the directory where you want the configuration
      # to be stored.
    # volumes:
    #   # Override all configuration:
    #   - type: bind
    #     source: /home/ledgersmb/conf
    #     target: /srv/ledgersmb/local/conf
    #   # Add a snippet of configuration:
    #   - type: bind
    #     source: /home/ledgersmb/conf/ledgersmb.100.yaml
    #     target: /srv/ledgersmb/local/conf/ledgersmb.100.yaml
    networks:
      - internal
      - default
    # Comment the 'ports' section to disable mapping the LedgerSMB container port (5762)
    #  to the host's port of the same number. Mapping "5762:5762" makes LedgerSMB
    #  available on http://<host-dns-or-ip>:5762/
    #     SECURITY NOTE:  Leave this uncommented for evaluation purposes only!
    #       In production, be sure to use SSL/TLS (such as by reverse proxying) to protect 
    #       user's passwords and other sensitive data
    ports:
      - "5762:5762"
    environment:
      # The LSMB_WORKERS environment variable lets you select the number
      # of processes serving HTTP requests. The default number of 2 workers
      # is geared toward limited-memory situations (1 GB). In order to
      # improve the performance experience, increase memory and the
      # number of workers
      #
      LSMB_WORKERS: ${LSMB_WORKERS:-5}
      #
      #

      # LSMB_MAIL_SMTPHOST:
      # LSMB_MAIL_SMTPPORT:
      # LSMB_MAIL_SMTPTLS:
      # LSMB_MAIL_SMTPSENDER_HOSTNAME:
      # LSMB_MAIL_SMTPUSER:
      # LSMB_MAIL_SMTPPASS:
      # LSMB_MAIL_SMTPAUTHMECH:
      #
      #
      # The PROXY_IP environment variable lets you set the IP address
      # (range) of the reverse proxy used for TLS termination, which forwards
      # its requests to this container. When this reverse proxy runs on the
      # Docker host, the default below applies. In case the reverse proxy is
      # 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
# that, the data is contained in the same volume as
# the rest of the image and on update/upgrade, the
# data will be lost.
volumes:
  pgdata:


networks:
  internal:

--------------------  >8  ------------------------


Cheers, István


2025. 03. 25, kedd keltezéssel 18.42-kor Harald Bader ezt írta:

For some functionalities i ll get: Invalid server response: document lacks BODY tag (as an example taxes in settings)
What is wrong what can i do??

Thx Harald
_______________________________________________
devel mailing list -- ..hidden..
To unsubscribe send an email to ..hidden..
_______________________________________________
devel mailing list -- ..hidden..
To unsubscribe send an email to ..hidden..