Update Debian System

sudo apt update sudo apt -y full-upgrade sudo systemctl reboot

Install

sudo apt install wget apt-transport-https gnupg2 libimlib2 libimlib2-dev -y

add Elasticsearch repository

wget -qO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo apt-key add -

echo "deb https://artifacts.elastic.co/packages/oss-7.x/apt stable main" | sudo tee /etc/apt/sources.list.d/elastic-7.x.list

sudo apt update

Install MariaDB and Apache Web Server

sudo apt install wget apt-transport-https gnupg2 libimlib2 libimlib2-dev

sudo apt install locales

sudo locale-gen de_DE.UTF-8

echo "LANG=de_DE.UTF-8" | sudo tee /etc/default/locale

sudo apt install mariadb-server

sudo mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MariaDB to secure it, we'll need the current
password for the root user.  If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none):
OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.

Set root password? [Y/n] y
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
 ... Success!


By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them.  This is intended only for testing, and to make the installation
go a bit smoother.  You should remove them before moving into a
production environment.

Remove anonymous users? [Y/n] y
 ... Success!

Normally, root should only be allowed to connect from 'localhost'.  This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n] y
 ... Success!

By default, MariaDB comes with a database named 'test' that anyone can
access.  This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n] y
 - Dropping test database...
 ... Success!
 - Removing privileges on test database...
 ... Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n] y
 ... Success!

Cleaning up...

All done!  If you've completed all of the above steps, your MariaDB
installation should now be secure.

Thanks for using MariaDB!

sudo systemctl restart mariadb

sudo apt install apache2

Install Zammad

wget -qO- https://dl.packager.io/srv/zammad/zammad/key | sudo apt-key add -

echo "deb https://dl.packager.io/srv/deb/zammad/zammad/stable/debian 10 main" | sudo tee /etc/apt/sources.list.d/zammad.list

sudo apt update

sudo apt install zammad

Elasticsearch install attachment plugin

sudo /usr/share/elasticsearch/bin/elasticsearch-plugin install ingest-attachment

Konfiguration Zammad

sudo /usr/share/elasticsearch/bin/elasticsearch-plugin install ingest-attachment

sudo systemctl start zammad

sudo systemctl enable zammad

sudo zammad run rails r "Setting.set('es_url', 'http://localhost:9200')"

sudo zammad run rake searchindex:rebuild

sudo a2dissite 000-default.conf

sudo systemctl restart apache2

potenzielle Fehler

“apachectl[2095]: Invalid command ‘RequestHeader’, perhaps misspelled or defined by a module not included in the server configuration“

Lösung

sudo vim /etc/apache2/sites-enabled/zammad.conf
# Line 36
#RequestHeader unset X-Forwarded-User

3.2.x: CSRF token verification failed

Lösung

sudo vim /etc/apache2/sites-enabled/zammad.conf

RequestHeader set X_FORWARDED_PROTO 'https' 
RequestHeader set X-Forwarded-Ssl on

a2enmod headers

systemctl restart apache2

Zammad

Inhaltsverzeichnis