Migrate config to globalvariables
See original GitHub issueThere are currently only a few values in config
. I propose we remove “config” completely and migrate these values to globalvaribles.
This removes two locations (config and globalvariables) that developers have to modify when starting SmokeDetector and allows us to remove a ConfigParser import that is only used at start up.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Avoiding Global Variables For Configuration File Reading in C
First of all, if the values are read once and never changed after that, then storing them as global variables is not a...
Read more >Transferring Configuration Files to a New Version of TestStand
How do I do this? TestStand saves all of its configuration data, including Station Global Variables, Users and Templates, as .ini files in...
Read more >Import global variable,connection, adapter from other server ...
I'm setup git with intergration server, problem here is it take too much time to setup local IS Now in my server have...
Read more >Manipulate Global Variables
Double-click on the global variable in the Configuration Components Pane. (Right-clicking then clicking Properties also works) · Enter the new value for your ......
Read more >How do I share global variables across modules - python
The best way to share global variables across modules across a single program is to create a config module. Just import the config...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We should let as many things be empty as possible. The fewer things you have to set before running the bot, the easier it is to get started.
I am happy with environment variables and default fullbacks for both location and the chat prefix strings.
The MSkey should allow for nonexistence (since I don’t run MS locally when testing smokey). On Jul 8, 2016 12:57 PM, “Undo1” notifications@github.com wrote: