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

Re: CLI Args and Config Files: Best Practices? (documented)

by Anonymous Monk
on Feb 01, 2013 at 09:24 UTC ( #1016484=note: print w/replies, xml ) Need Help??


in reply to CLI Args and Config Files: Best Practices?

What would be the best practice within AppConfig for enforcing the case I described initially - that is, CLI args are loaded at script startup and preserved throughout execution despite reloading from the config file with each lifecycle of the daemon?

I imagine do whatever makes sense to you, and document it

Take a look at the defaults of Daemon::Generic, you could (in your subclass) inject a --preserveargv or --discardargv option ...

Document whatever you choose, documentation is key

  • Comment on Re: CLI Args and Config Files: Best Practices? (documented)

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1016484]
help
Chatterbox?
[Corion]: I have Thursday and Friday off, so then I might get to converting the rough outlines to more articles ;)
[Corion]: But currently, most of the modules are web-related and I don't like to publish two web articles in a row
[Corion]: Maybe I should do the Filter::Simple release on the next weeked - this would give me one more article to milk from this theme

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (6)
As of 2017-04-24 08:57 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    I'm a fool:











    Results (437 votes). Check out past polls.