Talk:Zabbix - cgi and mysql - Revision history

Nangel: Nangel moved page Talk:Zabbix to Talk:Zabbix - cgi and mysql without leaving a redirect: As alpineuser mentioned, this page significantly changed the original - moving to a separate page

2021-10-12T13:31:50Z

Nangel moved page Talk:Zabbix to Talk:Zabbix - cgi and mysql without leaving a redirect: As alpineuser mentioned, this page significantly changed the original - moving to a separate page

← Older revision	Revision as of 13:31, 12 October 2021
(No difference)

Zcrayfish: /* Possible Obfuscation / Abuse */

2021-10-10T21:11:26Z

Possible Obfuscation / Abuse

← Older revision		Revision as of 21:11, 10 October 2021
Line 10:		Line 10:

	Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.		Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.

			<!-- Template:Unsigned --><span class="autosigned" style="font-size:85%;">— Preceding unsigned comments added by [[User:Alpineuser\|Alpineuser]] ([[User talk:Alpineuser#top\|talk]] • [[Special:Contributions/Alpineuser\|contribs]]) 10:21, 20 July 2021</span>

Alpineuser: /* Possible Obfuscation / Abuse */

2021-07-20T14:21:35Z

Possible Obfuscation / Abuse

← Older revision		Revision as of 14:21, 20 July 2021
Line 5:		Line 5:

	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. It is written with spelling errors/rushed, has non-idiomatic use of sed (# instead of / dividers), and lists non existent links like alpine newbie lamers, and refers to zabbix as a curse.		complexity, or is this obfuscation? It looks like the latter. It is written with spelling errors/rushed, has non-idiomatic use of sed (# instead of / dividers), and lists non existent links like alpine newbie lamers, and refers to zabbix as a curse. It's also much more LOC.

	Consider that I tested the old guide, and it works fine (v3.14) 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 (v3.14) 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.

	Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.		Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.

Alpineuser at 14:21, 20 July 2021

2021-07-20T14:21:21Z

← Older revision		Revision as of 14:21, 20 July 2021
Line 5:		Line 5:

	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. It is written with spelling errors, has non-idiomatic use of sed (# instead of / dividers), and lists non existent links like alpine newbie lamers, and refers to zabbix as a curse.		complexity, or is this obfuscation? It looks like the latter. It is written with spelling errors/rushed, has non-idiomatic use of sed (# instead of / dividers), and lists non existent links like alpine newbie lamers, and refers to zabbix as a curse.

	Consider that I tested the old guide, and it works fine (v3.14) 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 (v3.14) 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.

	Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.		Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.

Alpineuser at 14:20, 20 July 2021

2021-07-20T14:20:51Z

← Older revision		Revision as of 14:20, 20 July 2021
Line 5:		Line 5:

	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.		complexity, or is this obfuscation? It looks like the latter. It is written with spelling errors, has non-idiomatic use of sed (# instead of / dividers), and lists non existent links like alpine newbie lamers, and refers to zabbix as a curse.

	Consider that I tested the old guide, and it works fine (v3.14) 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 (v3.14) 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.

	Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.		Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.

Alpineuser at 14:19, 20 July 2021

2021-07-20T14:19:08Z

← Older revision		Revision as of 14:19, 20 July 2021
Line 5:		Line 5:

	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.

	Consider that I tested the old guide, and it works fine (v3.14) 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 (v3.14) 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.

	Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.		Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.

Alpineuser: /* Possible Obfuscation / Abuse */

2021-07-20T14:18:31Z

Possible Obfuscation / Abuse

← Older revision		Revision as of 14:18, 20 July 2021
Line 7:		Line 7:
	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.

	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.		Consider that I tested the old guide, and it works fine (v3.14) 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.

	Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.		Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.

Alpineuser: /* Possible Obfuscation / Abuse */

2021-07-20T14:18:15Z

Possible Obfuscation / Abuse

← Older revision		Revision as of 14:18, 20 July 2021
Line 8:		Line 8:

	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.		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.

			Given that the old guide will suffice for the majority of users, I suggest the old one is reinstated, and Mckagerhard's additions can be left as a second option for those interested in more details. The old guide uses fastcgi, and postgres. Mckagerhard's guide uses cgi, and mysql. Since they are distinct guides, they can be kept separate.

Alpineuser at 14:15, 20 July 2021

2021-07-20T14:15:58Z

← Older revision		Revision as of 14:15, 20 July 2021
Line 7:		Line 7:
	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.

	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.		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.

Alpineuser at 14:15, 20 July 2021

2021-07-20T14:15:50Z

← Older revision		Revision as of 14:15, 20 July 2021
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.