Zammad ticketing/helpdesk on Nethserver available

Update available!

  • zammad.conf - servername fixed
  • templated nginx zammad.conf
  • change port from 3000 to 3001 to safely coexist with ntopng
  • integrated to network services
  • app button
  • backup postgres db

Fresh install:

yum -y install https://mrmarkuz.goip.de/mirror/mrmarkuz/7/noarch/nethserver-mrmarkuz-0.0.1-3.ns7.noarch.rpm
yum -y install nethserver-zammad
config setprop zammad VirtualHost myserver.domain.local
yum -y install zammad
signal-event nethserver-zammad-update

Update:

yum -y update nethserver-zammad

2 Likes

Updated the initial install. All issues gone! Verified various config files and all ok.:slight_smile:

Your ‘trick’ by using the db key value of the virtual host for the app button should be integrated into all apps. Most of them (if not all) are hardcoded I guess.

Many thanks again!

2 Likes

Thanks again for testing!

I copied it from nethserver-mattermost.
With a virtualhost a db value is used.
In most other cases the browser url host is used and just “/appname” appended.

2 Likes

One more thing… :wink:

If I disable (config setprop zammad status disabled) zammad followed by signal-event nethserver-zammad-update, the httpd zammad.conf is still in place, where I would expect it to be removed.

After the above, and manually removing the zammad.conf file, the signal-event re-generates the zammad.conf file.

Would it be more consistent to have the signal-event check the status and thus will or will not generate the zammad.conf file?

Visiting the zammad virtualhost (e.g. zammad.myserver.com) now leads to and error message when zammad is set to disabled.

HTH

1 Like

Yes it would so I updated the module.
The zammad.conf is still generated as it’s a template but it gets emptied now when zammad is disabled.
Visiting the zammad virtualhost now shows the Nethserver page.

I added a Zammad wiki page.

1 Like

I’ve updated the module and can confirm the zammad.conf file is now ‘empty’ when status is set to disabled.

Again, many thanks. It now appears to be a very robust module.

1 Like

You’re welcome, thanks for testing.

@mandcsharma, seems the module is ready. :grinning:

2 Likes

Ehy guys! Great job. Wow a lot of testing and code here.
As we said at the conference in bruxelles in our community people ask things and most likely they get it
Kudos @mrmarkuz and @LayLow

2 Likes

Bravo guys, great job as usual :clap::clap::clap:

2 Likes

I found out that Zammad has a backup/restore script usable for cron so I updated the module.

  • Integrated daily backup cron jobsaves db and files for 10 days
  • Fixed restore-data procedure
  • Tested both (Nethserver and Zammad) backup/restore methods

This way we have another file/db backup if something goes wrong.

2 Likes

I can verify that all works fine!

Thanks.

2 Likes

Tested the Telegram integration option. Works like a charm. Inbound Telegram messages get delivered within seconds to Zammad and replies from Zammad to Telegram the same. Very cool!

https://zammad-admin-documentation.readthedocs.io/en/latest/channels-telegram.html

2 Likes

Kudos Markus, Zammad works brilliantly. Even better than I expected. :clap::clap::clap::clap::clap:

1 Like

FYI: https://community.zammad.org/t/zammad-3-1-is-there/2781

1 Like

Happy to see such projects improving and growing

1 Like

@mrmarkuz,

Is the wiki and packages from your repo up to par with latest elasticsearch (6 or 7) and Zammad 3.x series please?

I want to perform a new installation, and would like to use the latest :slight_smile:
TIA!!

1 Like

Zammad should always be the latest version, 3.1 actually.
Elasticsearch version 5.6.15 is used and supported, see Zammad docs. Do you think we should try a newer version?

1 Like

The new status and supported versions of Elasticsearch are mentioned here https://community.zammad.org/t/zammad-3-1-is-there/2781. However, Elasticsearch is also used in combination with OnlyOffice, so some consideration must be there I guess.

I guess experimenting with Elasticsearch 6/7 can not hurt, but a ‘must’, NO, absolutely not. But then again, I am not experienced enough with Elasticsearch.

Just giving this subject a spin to see if we can progress towards Zammad 3.x series.

Thanks for any considerations!!

1 Like

Zammad 3.1 is already used when installing the module. I’ll test newer elasticsearch and report.

EDIT:

It seems to work with Elasticsearch 7.2 in a first test. Here are the install/update steps to test the new version:

yum -y install https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.2.0-x86_64.rpm
yum -y install https://mrmarkuz.goip.de/mirror/devtest/nethserver-zammad-1.0.0-5.ns7.noarch.rpm
config setprop zammad VirtualHost zammad.domain.local
yum -y install zammad
signal-event nethserver-zammad-update
3 Likes

That all seems to work without any issue… Latest Zammad, and latest Elasticsearch installed.

Massive thanks @mrmarkuz !!

2 Likes