configuration-files

I would like to change the file octave-workspace from my home directory, simply renaming it to .octave_workspace . How can I manage to make octave recognize a workspace file (or create a new one) with this new name? Thanks. That is the purpose of the octave_core_file_name() function. Add the following to your .octaverc file: octave_core_file_name (".octave-workspace") OSX Solution: You can use chflags To hide a file from Finder: chflags hidden /Path/To/File To unhide: chflags nohidden /Path/To/File Linux Solution: From what I'm reading here, you can create a "hidden" files file, which contains

I often have to modify files such as sysctl.conf , and I'm familiar with using sed to replace existing values. Is there a way to append the new key/value pair to the file if sed wasn't able to replace it? For instance, using this example: modify config file using bash script sed -c -i "s/\($TARGET_KEY *= *\).*/\1$REPLACEMENT_VALUE/" $CONFIG_FILE How could I add the $TARGET_KEY = $REPLACEMENT_VALUE new line to $CONFIG_FILE using the same sed expression with slight changes? And on a related topic, how can I force creation of $CONFIG_FILE if it didn't exist? You can't easily do it all in a single

ASP.NET Core documentation suggests we should use appsettings.json file, along with a file per environment, containing overriding values. The problem is that all these files are published, though only appsettings.json and appsettings.[Environment].json are relevant. The other problem is that to change a config value on server one must inspect both files: base and environment specific. So my question is: what is the cleanest way to have one configuration file in each deployment environment? The key difference is that ASP.NET Core apps are not deployed for a particular configuration, as ASP.NET

My question is a duplicate of this one , but more detailed. The problem is that I have a BROKER_URL set in my Celery config file, but that isn't reflected in and I am loading the config: I checked, and it is being loaded - in fact, other constants defined there are being set, just not BROKER_URL . This appears to be a bug, but I wanted to be sure. celeryconfig.py : BROKER_URL = "amqp://user:password@remote.server.com:5672//vhost" CELERY_TASK_SERIALIZER = 'json' CELERY_RESULT_SERIALIZER = 'json' CELERY_ENABLE_UTC = True ( JSON is being used as the serializer, not Pickle , so I know this is

Is there any interest to use XML over YAML for each of these types of file: config security routing services translations I would like to ask XML vs YAML and JSON globally, but I'll stick to these topics :) Vitalii Zurian In my company projects for each of mentioned above points we use YAML because it is more readable. The most readable. The readablest. EDIT : The only abstract situation I can imagine for using XML over YAML - is probably for some dynamic file writers, since it is easier to manipulate with nodes using SimpleXML or something like that. For example, if you need to define some

I really enjoyed the new Configuration feature of Asp.Net vNext using de default appsettings.json But I would like to change the values of that file when I publish the website as a Azure Web App. The old web.config appsettings was easy to change and configure the properties on the environment. Do you know how to do this? I prefer to user the default provider instead of creating a custom configuration provider. Thank you! If you set App Settings in the Azure Portal, they become environment variables at runtime, and should get picked up by the ASP.NET vNext runtime. So you don't need to

I have read the documentation for this element but still fail to understand what its purpose is. Here is a sample of how I've seen it used in examples: <serviceHostingEnvironment> <baseAddressPrefixFilters> <add prefix="http://localhost:5100/"/> </baseAddressPrefixFilters> </serviceHostingEnvironment> I want to understand what this does that the base addresses in a service node doesn't do. I don't understand what this element is actually used for. Maurice A WCF service host will only allow a single base address per scheme (HTTP in this case). Now if you deploy a WCF service on an IIS