NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
For the record... (Score:1)
* Cheaper than a virtual.
* 90% of the features I need (svn servers, cron, shell)
* Unreachable disk and traffic limits.
* Control panel that doesn't suck.
* As many domains and shell users as I want.
It's a great place to shove lots and lots and lots of generic or bulky stuff where CPU doesn't matter, distribute large binary packages, hold all my system backups, store my SVN repositories (except for svn.ali.as) and general get stuff done.
It is, however, NOT the place w
Re: (Score:1)
Re:For the record... (Score:1)
I do see nigglies though, that makes me doubt some of their back-end competency.
Archived log files that don't get chowned and are stuck as owned by root.
Root-owned site paths no cleaned up when websites are dropped.
Etc etc... No major impacts, but certainly warnings signs.
And they are hiring a Perl coder. I'd almost be curious to go do a 6 month or 1 year stint with them.
Sort of a flash back to my youth, my first ever programming job was hosting company backend automation...
Reply to This
Parent