anchor.diff:        name: "database"
   ----
   ====
  -* Set xref:compute_resources.html#dev-compute-resources[memory, CPU], and xref:../architecture/additional_concepts/storage.html#pvc-resources[storage] default sizes to make sure your application is given enough resources to run smoothly.
  -
  -* Avoid referencing the `latest` tag from images if that tag is used across major versions. This may cause
  -running applications to break when new images are pushed to that tag.
  -
  -* A good template should build and deploy cleanly without requiring modifications after the template is deployed.
  +* Set xref:compute_resources.adoc#dev-compute-resources[memory, CPU], and
  +xref:../architecture/additional_concepts/storage.adoc#pvc-resources[storage]
  +default sizes to make sure your application is given enough resources to run
  +smoothly.
  +
  +* Avoid referencing the `latest` tag from images if that tag is used across major
  +versions. This may cause running applications to break when new images are
  +pushed to that tag.
  +
  +* A good template builds and deploys cleanly without requiring modifications
  +after the template is deployed.
   
   
   [[export-as-template]]
  
positive.code: message: "Your admin credentials are ${ADMIN_USERNAME}:${ADMIN_PASSWORD}" <6>
  ----
  <1> The unique name of the template.
  <2> A user-friendly name, which can be employed by user interfaces. This should be short.
  <3> A description of the template. Include enough detail that the user will understand what
  is being deployed and any caveats they need to know before deploying. It should also provide links
  to additional information such as a README. Newline characters `\n` can be included to create paragraphs.
  <4> Tags to be associated with the template for searching and grouping. Add tags that will include it into one
  of the out of the box catalog categories.  Refer to the `id` and `categoryAliases` in `CATALOG_CATEGORIES` in the console's
  https://github.com/openshift/origin-web-console/blob/master/app/scripts/constants.js[constants file]. The categories can also be
  xref:../install_config/web_console_customization.html#configuring-catalog-categories[customized] for the whole cluster.
  <5> An icon to be displayed with your template in the web console. Pick from our existing
  https://rawgit.com/openshift/origin-web-console/master/app/styles/fonts/openshift-logos-icon/demo.html[logo icons]
  when possible. Icons from http://fontawesome.io/icons/[FontAwesome] and https://www.patternfly.org/styles/icons/[Patternfly]
  can also be used. Alternatively provide icons through xref:../install_config/web_console_customization.html#loading-custom-scripts-and-stylesheets[CSS customizations]
  that can be added to an OpenShift cluster that uses your template. You must specify an iconClass that exists
  or it will prevent falling back to the generic icon.
  <6> An instructional message that is displayed when this template is instantiated.
  This field should inform the user how to use the newly created resources.
  Parameter substitution is performed on the message before being displayed so
  that generated credentials and other parameters can be included in the output. Include links to any
  next steps documentation that users should follow.
  ====
  
  [[writing-labels]]
  
negative.code: [[other-recommendations]]
  === Other Recommendations
  
  * Group related services together in the management console by adding the
  `service.alpha.openshift.io/dependencies` annotation to the Service object in
  your template.
  +
  .Group the Frontend and Database Services Together on the Management Console Overview
  ====
  [source,yaml]
  ----
  