Is it plausible to use a filesystem-based configuration format rather than an INI file?
After having had endless issues with INI-style configuration files and parsing them correctly (let along getting binary data right), a crazy idea crossed my mind recently:
How many different configurations are used for software tests? [closed]
Closed 10 years ago.
Configuration file that can be modified by user in C#
I want to create a configuration file (text file preferred) that can be modified by user. A windows service will read from that file and behave accordingly. Can you recommend a file format for this kind of process?
What I have in my is a config file like the game config files, but could not imagine how to read from it.
How to make big chunk of hardcoded menuitems in a programmable way
So in the javascript app, we have a lot of repeated chunk of menu items with the specific settings: URL, Name, Title, etc etc (these settings sometimes can be optional). Here is the gist of the menuItem and we have tons of them.
What is the best way to store configurations of shell/script code to execute later?
I am working on a tool (Python, may or may not be important) that will allow a user to maintain a configuration file containing arbitrary shell and/or language code to be executed on particular events and intervals. The code will potentially involve multiple statements.
What is the best way to store configurations of shell/script code to execute later?
I am working on a tool (Python, may or may not be important) that will allow a user to maintain a configuration file containing arbitrary shell and/or language code to be executed on particular events and intervals. The code will potentially involve multiple statements.
What is the best way to store configurations of shell/script code to execute later?
I am working on a tool (Python, may or may not be important) that will allow a user to maintain a configuration file containing arbitrary shell and/or language code to be executed on particular events and intervals. The code will potentially involve multiple statements.
What is the best way to store configurations of shell/script code to execute later?
I am working on a tool (Python, may or may not be important) that will allow a user to maintain a configuration file containing arbitrary shell and/or language code to be executed on particular events and intervals. The code will potentially involve multiple statements.
What is the best way to store configurations of shell/script code to execute later?
I am working on a tool (Python, may or may not be important) that will allow a user to maintain a configuration file containing arbitrary shell and/or language code to be executed on particular events and intervals. The code will potentially involve multiple statements.
Specifying options “hard coded”, in an interpreted language
In a language like Python or JavaScript (NodeJS), is there anything wrong with defining “the configuration file” as a file which essentially hard-codes the configuration settings? For example: