Zammad doesn't use external database

  • Used Zammad version: 6.3.1
  • Used Zammad installation type: package
  • Operating system: Ubuntu 24.04 Server (AMD64)
  • Browser + version: Vivaldi 6.9

Expected behavior:

  • Zammad connects to the database specified in database.yml file and creates tables, etc. during first steps.

Actual behavior:

  • Zammad uses its localhost database, instead of the one specified in database.yml file.

Steps to reproduce the behavior:

  • Install Zammad on a cloud provider virtual machine (AWS EC2)
  • Install libimlib2, nodejs, redis-server, rvm (+ Ruby 3.2.4), nginx, postgres-client-16, elasticsearch, zammad
  • Attach persistent volume (AWS EBS), copy database.yml to opt/zammad/config/database.yml and zammad.conf to /etc/nginx/sites-available/zammad.conf
  • run rails r ‘Rails.cache.clear’
  • restart zammad service
  • reload nginx

What am I missing? The documentation does not state any steps as to use an already existing database file, instead of creating that localhost-pointing database.yml by default.

Thank you in advance.

Sorry but what’s your installation type now?

It’s still the package installed via Ubuntu apt install. The disk is there to store configuration files, because AWS virtual machines wipe their root volume on boot, thus losing all data on the disk every restart.

These are purely automation steps on my part, which do not impact the install itself, but rather interact with the OS to have an external disk mounted.

This is the default database.yml - you can provide a host and port parameter if needed: