Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
For larger web projects, sometimes it helps to create a set of Unix-ish directories and build from there:
$app/bin your main script and/or associated utilities $app/etc configuration files, persistent state $app/lib all of your modules or 3rd-party modules you need to bundle $app/var any misc. state or files you create/use at run-time (if any) $app/doc documentation (though a README or INSTALL would be nice in $app/) $app/htdocs the web 'root' of your application, attached to your web site using server configuration
Keep in mind that though it's a common practice to stick all of your CGI scripts in a /cgi-bin/ directory, it's not necessarily the best practice. Most web servers will let you drop a script.cgi directly into your document root, (and if you're extension-conscious, Apache's MultiViews or another content negotiation mechanism could allow you to link to it just as "script"), which could help with URI UI issues.

Sometimes this is overkill (and it sounds like it might be for this particular project), but this is useful for keeping stuff organized and allows a project to be completely self-contained and portable.


In reply to Re: How to organize a CGI project? by Fastolfe
in thread How to organize a CGI project? by weini

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others having an uproarious good time at the Monastery: (3)
As of 2024-04-16 14:23 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found