configuration-management

Let's say there is a file called myfile.java. I checked it out and I was working on it. Before checking it in, I have lost my hard drive and I had to get a new hard drive. Next time that I want to check out the file, it says that I can not check out. It was already checked out in the old view which has gone. I have to mention that I am using the option "re-use development stream option". Is there anything I can do to be able to checkout the file once again? You can completely unregister your old view in the vob of that file: that will remove the "checkout" status associated to that file.

I created a complex state for API service, it involves git checkouts, python venv, uwsgi, nginx, etc etc. It works fine. Now I would like to turn it into a template and execute it several times per minion, with variables supplied from pillar - i.e something like. {% for apiserver in pillar.apiservers %} include apiserver_template.sls, locals: apiserver.config {% endfor %} where apiserver_template will work with context supplied to it, with apiserver.config having all config data for each API instance. I know syntax is wrong but hopefully I am communicating the idea - ideally, something like

I'm developing a C# WPF MVVM application with .NET Framework 4.6.1 and I have a custom section in App.config: <configuration> <configSections> <section name="SpeedSection" type="System.Configuration.NameValueSectionHandler" /> </configSections> <SpeedSection> <add key="PrinterSpeed" value="150" /> <add key="CameraSpeed" value="150" /> </SpeedSection> </configuration> I want to modify PrinterSpeed and CameraSpeed from my app. I have tried this code: static void AddUpdateAppSettings(string key, string value) { try { var configFile = ConfigurationManager.OpenExeConfiguration

I would like to build the same project twice in the same solution configuration, varying some #define flags to toggle features. Both binaries will be deployed with different names. The solutions that I know could work: Add a solution configuration - But I will then need to build the solution twice, which I would prefer to avoid. Both project configurations will always be built. Copy the project - But then I have the overhead of maintaining a new project when I only want to maintain a different configuration. Batch build - I avoid using batch build as I use both devenv for local development and

Closed . This question is opinion-based. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it can be answered with facts and citations by editing this post . I am trying to find the best method for white labeling an Android application. Basically I want to be able to build multiple versions of almost the same app, each version will have different resources (e.g. drawable icons, colors, etc.) but they will share a lot of the code base. Some of the apps will have additional features as well, so they won't just be clones of each other. One