User Configuration of a Shell Script. Best practices?
I am writing a shell script with a few variables that should be configured by the user. There will be an installer for downloading and configuring the script, possibly by asking a series of question. The script in question is aimed at other developers.
technique for checking modifications in configuration file while starting up a program
I’m writing a software for periodically checking a specific range of networked devices’ reach-ability. I’m specifying the address range and the time frequency for checking their reachability, in an xml file. Which technique can I use to check that xml file during the start up of the program for any modifications done in either the range or the frequency and do the necessary update in specific database?
What problems do configuration management tools solve?
My company is creating a service in an Amazon Virtual Private Cloud. Without getting too much into the details, there will be about 5 different types of servers, and each type will need to be replicated based on demand. A bit of reading gives me the impression that we’re going to want to use a config management tool like Puppet or Chef.
What’s a good strategy for managing static data in an SOA?
I’m working on a web application that sits on top of a number of RESTful web services, interacting primarily with those services through JSON formatted messages over HTTP. Our application has a great deal of static data that are read from these services (internationalization lookups, configuration, etc.) during operation.
How to best distribute client specific configuration settings
I’m writing a WinForms desktop application which will be shipped out to several different clients and am wondering what the best way to implement a user configuration file is. Normally I would use the built in Settings.settings
or app.config
to store user settings but in this case what I want to store is unique for every client, I want it to be configured before sending it out and I want to avoid recompiling every time we ship to a new client.
Who should support and maintain development infrastructure?
I am interested to know what other peoples’ experiences are with managing development infrastructure are. I am talking about things like the build server, the central git repo etc etc. Any infrastructure which end users would probably not even know existed, but which are essential for the development team.
alternative to environment variables
The amount of servers and the complexity of our application is growing and we now have servers in different regions (hosted on AWS). Certain database operations require low latency so we have stuck a database in each region (which is basically a user cache) to keep the network latency low. The way the application server currently knows which user cache/database to make its call to depends on an environemnt variable set in it. This has been working fine, but it seems hacky and not optimal. Is there any way for this to be done automatically?
Source code “prints” at release
Is there a best practice for how to document the source code you’re releasing?
Source code “prints” at release
Is there a best practice for how to document the source code you’re releasing?
Source code “prints” at release
Is there a best practice for how to document the source code you’re releasing?