The only thing I can speculate is that it's a marker for the base directory -- but that would be odd since there's a method for that. On the other hand, I do usually always have such a dot-file marking the root of my app installation on the FS, so that scripts know where to look for library paths, and so on. Most of my scripts start with something like: 

BEGIN {
    use Path::Tiny;
    my $base = path(__FILE__)->parent;
    $base = $base->parent until -f "$base/.some-dot-file" or $base->is
+_rootdir;
    unshift @INC, "$base/lib";
}

[download]
... so that they don't have to know where they live. Possibly .dancer has or once had a purpose like that?


The way forward always starts with a minimal test.

In reply to Re^3: .dancer -- what's it for by 1nickt
in thread .dancer -- what's it for by kcott

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.