Talk:Zabbix - cgi and mysql: Difference between revisions

From Alpine Linux
No edit summary
No edit summary
Line 4: Line 4:
https://wiki.alpinelinux.org/w/index.php?title=Zabbix&type=revision&diff=19688&oldid=17984
https://wiki.alpinelinux.org/w/index.php?title=Zabbix&type=revision&diff=19688&oldid=17984


What was a 10 minute easy install is now a 30-60 minute ordeal. Can Mckaygerhard justify the need for this additional
Can Mckaygerhard justify the need for this additional
complexity, or is this obfuscation? It looks like the latter, upon first glance.  
complexity, or is this obfuscation? It looks like the latter, upon first glance.


I tested the old guide, and it works fine except that I had to copy the zabbix.conf.php from a different zabbix install to this since the database type doesn't populate during the setup.php install (essentially bypassing it). And the js on the web console only worked with certain browsers.
Consider that, I tested the old guide, and it works fine except that I had to copy the zabbix.conf.php from a different zabbix install to this since the database type doesn't populate during the setup.php install (essentially bypassing it). And the js on the web console only worked with certain browsers.

Revision as of 14:15, 20 July 2021

Possible Obfuscation / Abuse

It appears that someone has taken the article from a manageable <40 command line entries and 6K bytes to 20K bytes, and now command line entries that number 100-200+: https://wiki.alpinelinux.org/w/index.php?title=Zabbix&type=revision&diff=19688&oldid=17984

Can Mckaygerhard justify the need for this additional complexity, or is this obfuscation? It looks like the latter, upon first glance.

Consider that, I tested the old guide, and it works fine except that I had to copy the zabbix.conf.php from a different zabbix install to this since the database type doesn't populate during the setup.php install (essentially bypassing it). And the js on the web console only worked with certain browsers.