anchor.diff:  a|*_app.json_*, *_package.json_*
   
   a|`perl`
  -a|*_index.pl_*, *_cpanfile_*
  +a|*_cpanfile_*, *_index.pl_*
   
   a|`php`
  -a|*_index.php_*, *_composer.json_*
  +a|*_composer.json_*, *_index.php_*
   
   a|`python`
   a|*_requirements.txt_*, *_setup.py_*
   
   a|`ruby`
  -a|*_Rakefile_*, *_Gemfile_*, *_config.ru_*
  +a|*_Gemfile_*, *_Rakefile_*, *_config.ru_*
  +
  +a|`scala`
  +a|*_build.sbt_*
   
   |===
   
  
positive.code: cluster administrators must ensure that the Docker daemon on the {product-title}
  node hosts is run with the `--insecure-registry` flag pointing to that registry.
  You must also tell `new-app` that the image comes from an insecure registry with
  the `--insecure-registry=true` flag.
  ====
  
  You can create an application from an existing
  xref:../architecture/core_concepts/builds_and_image_streams.adoc#image-streams[image
  stream] and tag (optional) for the image stream:
  
  ====
  ----
  
negative.code: 
  [NOTE]
  ====
  If using a local Git repository, the repository should have a remote named
  *origin* that points to a URL accessible by the {product-title} cluster.  If
  there is no recognised remote, `new-app` will create a
  xref:builds.adoc#binary-source[binary build].
  ====
  
  You can use a subdirectory of your source code repository by specifying a
  