Scalr does! When using Scalr ConfigTemplates, you can easily make configuration changes for services such as MySQL and Apache. Scalr does the heavy work, pushing those changes out to your servers.
Scalr is even smart enough to know when a process should to be restarted after a configuration change. Plus, you can customize the process: you can organize configuration into ConfigTemplates and apply them to select servers. With this setup, you can have a ConfigTemplate for your dev/test MySQL servers and another one for your production servers.
Creating ConfigTemplates is easy thanks to a nifty web-based interface we built for it, as shown below.
Give your template a name (in this example it’s “MySQLconfig”), modify the values, and hit “Save.” Now that wasn’t so bad, was it?
Once you have a ConfigTemplate, you can apply it to your server farm’s roles.
Select the ConfigTemplate you want from the dropdown to apply.
By creating multiple ConfigTemplates and modifying existing ones, Scalr makes managing service configuration, well, manageable—it doesn’t matter if you have a single instance or hundreds of them. Doing this for Apache (or any other software) is just as easy. See for yourself:
Um, because they are awesome? Scalr is smart enough to know which configuration option changes require service restarts, and which ones don’t. So if you make a few changes to your config file, and don’t know whether you need to /etc/init.d/httpd restart–well, leave it up to Scalr.
