This is going to be a short one, but potentially useful for anybody writing a Dancer template module, or just plain curious about Dancer’s guts. So here goes.
A frequent inquiry concerning databases’ security is to retrieve the database role(s) associated with each user for auditing or troubleshooting purposes. Each database user (principal) can be retrieved from sys.database_principals and the associated database roles can be retrieved from sys.database_role_members The following code runs against ALL the databases using SP_MSForeachdb and all roles for one principal is concatenated in one row
Nagios Check For Calculating Based on Mysql Server Variables Recently we needed to make a change for a client to one of our mysql monitoring tools so I thought it would be a good opportunity to highlight the tool and discuss some of the changes that I made. You can access the tool on Github…
DuckFeet’s guts are SQLicious, and built as DBIx::Class classes, sprinkled with wonderfully tooth-decaying DBIx::Class::Candy on top. In the repo, it’s all under the DuckFeet::Schema namespace. For the time being, there is only a handful of tables (hits, uris, referers, agents and hosts), but it should be easily extendable to add any type of information we might desire to throw in, but it should be easily extendable to add any type of information we might desire to throw in.
Say hello to Template::Caribou. The goal of that new template system? Steal or be inspired by a maximal amount of Template::Declare features, while using Moose as the core engine. For the rest of this blog entry, I’ll take you on a tour of that basic sample use, peeling the system from the outside in, hoping that the glitter of the outer layers will soften the shocks of the abominations of the inner mechanisms.
I have been working on my game recently and wanted to check out how to dig some caves. Without readily available software to do my excavations, I decided to give it a shot myself. To come up with an algorithm to create a decent dungeon or cave system was the hard part. At the end, I went with a very simple recipe that seems to gives fair results.
Somebody at $work asked me how I use Git to deploy stuff, probably working under the false hypothesis that wisdom is in any way, shape or form affiliated with yours truly. The fool…Yet, it is true that I had my share of tinkering with Git, and that I might have gleaned from my experience. So I sent him a couple of links leading to more wisdom-certified sources. They are listed at the end of this blog entry; if you have more good articles/blog posts that you’d like to add to the pile, please don’t be shy and mention them in the comments. But I can’t just stop there, really. So, if you allow me, I’ll dust off the good ol’ soap-box, hop on it, and share my thoughts on the subject.
I have seen lots of questions floating in the msdn forums about SSPI Handshake error, the main question is around error code 0x80090311 which is indicative of the authentication failure error. Apart from this, there are many other reasons for SSPI Handshake error to appear in error logs. I cover them here.
A client running CentOS 5.4 Amazon EC2 instances needed the latest libMemcachedversion installed. With the inclusion of the “make rpm” target, libMemcached makes it easy to build the libMemcached RPMs by doing the following: Spin up a new CentOS Amazon EC2 instance, As root on the new instance: yum install @development-tools yum install fedora-packager /usr/sbin/useradd…
My colleages and I want to set up a LAN radio station, so that we can all groove to the same soundtrack. To make things interesting, we want to be able to dynamically add songs to the playlist. From any machine. And since I don’t really have time to do something like that, I’m setting myself a deadline of one evening to get it running. Got it? Good. For it’s time to rip our shirts. And dance the Haka.