Re: [Tiki-devel] GlitchTip, an error reporting tool

We do have a file for database credentials, we also have a lock file that is used and we also have ini file configuration support.

There is a somewhat frequent need to have a file based configuration. For example to specify a domain name, which can not be determined when running CLI commands, etc. 

It would be nice if there was a single place where all these things could be done. Right now there is a multitude of different solutions to deal with different issues. Your particular use case is one more use case that could benefit from this.

The ini file might be a way to solve this issue, although I presume it happens after autoloading. That is fairly early on, so maybe its ok? One direction might be to move everything to a single default ini file. Yes cascading of ini files could still be a thing. We could have some default vales in there to uncomment in order to enable, database credentials might work well in there etc. 

Other solutions might also be considered, but we already have ini support. Maybe an ini.php to eliminate the possibility of snooping? 

As for actions initiating on preference changes, yes this is done somewhat frequently in Tiki currently. The password blacklist looks for changes to password preferences to update the password files it uses. Every time preferences are saved, tiki checks out what changed and only updates those specific prefs, not everything on the page. Etc.  


Brendan

> On Apr 12, 2021, at 4:16 PM, Fabio Montefuscolo <[email protected]> wrote:
> 
> 
> Hi Brendan
> 
> I am glad I got your attention!
> 
> These "actions" you are talking about, they are ideas or that already exists on Tiki?
> 
> Bye bye :)
> 
> 
>> On Wed, Apr 7, 2021 at 4:51 PM Brendan Ferguson <[email protected]> wrote:
>> Actions can be initialized upon preference changes. Create a “flag file” or remove the “flag file” when the preference is created. Then check for the file to initialize.
>> 
>> This also ties into the creation of a tiki preference file. There seems to be a real need for it. We currently have a lock file, and now also “super admin” actions that require a file. We have our database configuration as well. This should be a line in that file somewhere. Ideally, that is.
>> 
>> My 3 cents.
>> 
>> Brendan
>> 
>> 
>> 
>>> On Apr 7, 2021, at 2:28 PM, Fabio Montefuscolo <[email protected]> wrote:
>>> 
>>> Dear community
>>> 
>>> I had a task about researching reporting tools and I ended up trying GlitchTip, that is a real OpenSource alternative to Sentry.
>>> 
>>> The tool is capable to catch unhandled exception and errors on many programming languages, including PHP and JavaScript.
>>> 
>>> After you wire GlitchTip to your site, the errors start to popup in the report page. We have a good amount of useful information, like the error stack trace, browser and OS version and some HTTP headers.
>>> 
>>> Tracking JavaScript errors is pretty easy. You just need to go to "Settings > Control Panels > Look & feel > Customization" and add GlitchTip code[1] into "Custom HTML head content".
>>> 
>>> But tracking PHP errors is not easy yet. We would need to change some bytes on Tiki code. Basically, to GlitchTip catch errors on PHP side we would need to add a library[2] and initialize the API as soon as possible, probably in tiki-setup or tiki-setup_base. Also, we need to keep somewhere the DSN code. If we store as preference, then that means the GlitchTip initialization will happen after loading preferences, and errors before that will not appear.
>>> 
>>> Does anyone have an idea about how to integrate GlitchTip library into Tiki? When is a good moment to initialize GlitchTip.
>>> 
>>> [1] - https://glitchtip.com/sdkdocs/javascript-browser
>>> [2] - https://glitchtip.com/sdkdocs/php
>>> 
>>> Thanks
>>> _______________________________________________
>>> TikiWiki-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>> 
>> _______________________________________________
>> TikiWiki-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
> _______________________________________________
> TikiWiki-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

_______________________________________________
TikiWiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel