Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
My current "design in progress" experimental web application environment makes heavy use of file paths to control what gets used where. Pretty much every file path from the config files, to the modules, to images, javascript source and CSS are searched and loaded as needed at run time according to first found in the path order. My production application is at the root of the search path in the "main" path. I run my test version with an extra "dev" path inserted before "main". Any file (including config files) not found in the "dev" path automatically fall back to the "main" path. When I start hacking up a new version, I copy each file I edit into the "dev" path as I need to touch it. In dev I can change anything I want, create new stuff and generally yank the application around while still using the existing prod code/data directly for anything not changing. At any time I can create a new path for testing/bugfixing/development and re-order paths on top of paths so I can test fixes on fixes.

It's actually alot slicker than my feeble description :)

More to your question, I routinely keep several different paths (main, test, dev) each with their own variation of config file (different databases, different login, different file paths). Even config file format changes between paths are not an issue.

In reply to Re: Single file oriented for different usage by ruzam
in thread Single file oriented for different usage by arbingersys

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 rifling through the Monastery: (7)
As of 2024-03-28 11:20 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found