in reply to Dancer2::Plugin::Database and database errors
It occurred to me that someone might ask why I don't just go back to using my own database code, and let it go. Good question; I have no answer. I figured that for this particular project, I'd use what appeared to be the "Dancer2 stuff" instead of writing my own. If no suggestions for getting around this come up, then I'll be forced to go back to doing my own.
This project answers on both API (using JSON) and straight web pages. At this time there is no authorization code at all, since it is strictly internal to our group. It is an interface between Nagios-XI and ServiceNow, but will also interact with other applications in the future (Slack/PagerDuty/etc). I also want to take the core code and publish it in github as an example for others who are writing APIs. So that is part of what made me thing I'd be better off using more "off the shelf" modules than writing my own.
David Lee Crites, Author and DevOps Dude
Devops: lee@critesclan.com
Author: davidlee@adoniah.co
quad alii ut vivere
|
|---|