DAdmin is a web application written in Perl to manage customers, domainnames, prices, pricegroups, topleveldomains, expirations, renewals, costs and so on. This web application is intended to be used by internet service providers who offer domain services to their customers and who need a way to manage their customers, their domainnames they registered/ordered and the prices associated to them.
DAdmin is based on Perl. It’s powered by mod_perl and uses the object-relational database management system Postgresql. For this project I made heavy use of self defined server side functions in PL/pgSQL to ease many aspects of getting the appropriate data. For example getting all domainnames that expire this and next month requires quite some joins or at least some nested subselects which is the downside of normalisation but having the serverside functions I could encapsulate all the selects and form an appropriate result set which then again can be used by my perl script to display the data e.g. Having all these select statements which I also had to repeat in my perl scripts would lead to unmaintainable code or at least less maintainable code. This way I simply call a serverside function and get my result set. However, I managed to get a new friend called Moose which is the post modern object system for perl and it helped me a lot to get an awful f*cking modular system which is scalable, very easy to maintain and very hard to misunderstand. At no point someone will think who the hell did this shit but think to just make the change, reload apache and have a nice day.
The idea of the project wasn’t just because I felt boring or mouldy. I had this project in mind >3 years ago when I started at this company I am currently working for. We, as in the company, offer domain services to our customers and the process to bill a domain name was quite fancy…imagine a customer that calls me and asks for a domain name to register…I tell the customer to send me an email with the desired domain name and I will then register it for him. I then have to tell my boss that customer X has ordered a domain name and that we have to bill him.
The problem here is that sooner or later no one really knew what domain names exist and could be billed so we ended up with a lot of domain names no one really paid for. At that time we had no system that informed us when a domain name is about to expire or to be renewed. But especially this info is very important for us because without this information we can’t bill the names.
So the motivation for DAdmin was born. The name DAdmin simply means “domain admin”
. However, I planned a web application that could manage the costs, the domain names, the customers etc…the result is DAdmin. Now also customers have an overview of their domain names and costs because they also now have a system to get in touch with us.
And DAdmin itself simply sends out reports which domain names are to be expired or renewed next and the month after so we can simply work down this list and bill the customers without losing any money.
DAdmin is based on Perl. It’s powered by mod_perl and uses the object-relational database management system Postgresql. For this project I made heavy use of self defined server side functions in PL/pgSQL to ease many aspects of getting the appropriate data. For example getting all domainnames that expire this and next month requires quite some joins or at least some nested subselects which is the downside of normalisation but having the serverside functions I could encapsulate all the selects and form an appropriate result set which then again can be used by my perl script to display the data e.g. Having all these select statements which I also had to repeat in my perl scripts would lead to unmaintainable code or at least less maintainable code. This way I simply call a serverside function and get my result set. However, I managed to get a new friend called Moose which is the post modern object system for perl and it helped me a lot to get an awful f*cking modular system which is scalable, very easy to maintain and very hard to misunderstand. At no point someone will think who the hell did this shit but think to just make the change, reload apache and have a nice day.
The idea of the project wasn’t just because I felt boring or mouldy. I had this project in mind >3 years ago when I started at this company I am currently working for. We, as in the company, offer domain services to our customers and the process to bill a domain name was quite fancy…imagine a customer that calls me and asks for a domain name to register…I tell the customer to send me an email with the desired domain name and I will then register it for him. I then have to tell my boss that customer X has ordered a domain name and that we have to bill him.
The problem here is that sooner or later no one really knew what domain names exist and could be billed so we ended up with a lot of domain names no one really paid for. At that time we had no system that informed us when a domain name is about to expire or to be renewed. But especially this info is very important for us because without this information we can’t bill the names.
So the motivation for DAdmin was born. The name DAdmin simply means “domain admin”
. However, I planned a web application that could manage the costs, the domain names, the customers etc…the result is DAdmin. Now also customers have an overview of their domain names and costs because they also now have a system to get in touch with us.
And DAdmin itself simply sends out reports which domain names are to be expired or renewed next and the month after so we can simply work down this list and bill the customers without losing any money.
DAdmin
Copyright (C) Andreas Schipplock
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
Support for DAdmin
The easiest and most transparent way to get support is to use the mailing list provided by google. Just subscribe and mail your question or problem. Me or another nice guy or girl then is going to help you as much as possible. Just keep in mind that the primary language used there is english.