Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • For me DreamHost fills the following niche.

    * 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
    • I realize its discount shared hosting. But thus far, DH has had serious problems delivering simple static pages, not to mention email. Even discount shared hosting has certain minimum requirements. A great config panel isn't much use if no one can view your website. E.g., in response to everyone's support tickets for the *latest* issue, the response included this happy little tidbit (posted on 3/23):

      Some of you are also asking when this issue will be fixed, I wish I had concrete information for you, but i

      • I assume I've been relatively lucky, because only one of the outages impacted me, and that's the first time I've seen it go down in the entire time I've been hosting there.

        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...