anchor.diff:        .mapConfigResource(o.getName(), "classpath:a/b/qa.yml");
   ----
   
  -* Specifying a config file on command line. Each Bootique app supports `--config` option that takes a configuration file as its parameter. To specify more than one file, use `--config` option multiple times. Configurations will be loaded and merged together in the order of their appearance on the command line.
  +* Specifying a config file on the command line. Each Bootique app supports `--config` option that takes a configuration
  +file as parameter. To specify more than one file, use `--config` option multiple times. Configurations will be loaded
  +and merged together in the order of their appearance on the command line.
   
   * Specifying a single config value via a custom option:
   +
  
positive.code:       .mapConfigPath(o.getName(), "jdbc.mydb.url);
  ----
  +
  This adds a new `--db` option to the app that can be used to set JDBC URL of a datasource called "mydb". If value is not specified, the default one will be used.
  
  ==== Configuration via Properties
  
  
negative.code: }
  ----
  
  The factory contains configuration property declarations, as well as public setters for these properties. (You may
  create getters as well. It is not required, but may be useful for unit tests, etc.). Now let's take a look at the
  Module class:
  
  [source,java]
  ----
  public class MyModule extends ConfigModule {
  
      @Singleton
      @Provides
      public MyService createMyService(
               ConfigurationFactory configFactory,
               SomeOtherService service) {
  
          return config(MyFactory.class, configFactory).createMyService(service);
      }
  }
  ----
  
  A sample configuration that will work with our module may look like this:
  
  [source,yaml]
  ----
  