dancing with perl – part 2

Almost a year after I first wrote about dancer, I finally got around to building my first site with it. Overall, it is a pretty nice little framework. If you are already familiar with perl and/or the template toolkit, then I highly recommend this for quickly deploying projects.

In my case, I was able to build and deploy a management interface for a smartos zone server in just a few hours. I fleshed it out over the course of a week or so, and how it is in production managing dozens of zones quite easily. The interface talks to a mysql database, a node.js server I wrote as part of the same project, and even manages a local haproxy instance. All of this in such a tiny space that I keep getting weirded out.

In the future I’ll document some of the pitfalls and oddities that I experienced. I found that once I came around to the dancer way of thinking, it got pretty easy and I’ve rarely had to address the documentation since.

dancing with perl – part 2

building a new mail server – planning

it has recently been heavily hinted to me that i might be tasked with building a new mail system soon, which got me thinking about how to do it better than i have before. i haven’t built a mail system from scratch in about a year, and there are some things i want to try that i either didn’t want to do last time, or didn’t have time to implement. my planning, design, and implementation process will be put here so that i have a future reference, and also in case it helps others.
Continue reading “building a new mail server – planning”

building a new mail server – planning

iphive – demo

i’ve got a demo instance of iphive running, so if you want to see how it works feel free to email me and i can get you access to try it out. the demo is using the latest version of the code as of 2011.4.4 and is using private address space for the example database.

the next version is being written to accommodate IPv6, and will also have better user-accounting facilities to better track the who-does-what aspect of inventory management. at that time i’ll also be upgrading to the newest version of the mite framework, which will unlock a whole slew of possible enhancements and improvements.

iphive – demo

fireverse

fireverse is a stellar conquest civ-type webgame. the current version (alpha6.2011.1.21) is written on top of the mite framework in perl, and uses mysql for a backend data model.

graphics are generated dynamically in svg format, though png conversion is available for those browsers that don’t support svg yet.

fireverse

mydns module – about

NB : The mydns project appears to be dead, and a new project has (sort of) taken its place (mydns-ng). With this in mind, the module discussed here should be considered of VERY limited use.

First of all, you need to go here so you have an idea of what this is about.
This is a perl module written to help manage a mydns based server.
The idea was to provide a simple and clean interface, which also means that there aren’t a lot of additional or optional things enabled or supported.
Still, this should get you by if you need to do a lot of bulk management duties.

note – this project was pretty much abandoned ones I put together my own dnsadmin system to manage bind rather than mydns. This isn’t to say bind is better than mydns, but rather that the environment I deployed these in preferred bind.

here is the pod2html output for the module :
MyDNS

here is the module itself :
MyDNS.pm

mydns module – about