Sample Applications

Sample Applications is a collection of ready-to-run applications which can be deployed to Helion Stackato with a couple of clicks. This interface uses the same API as the CLI client, pulling the source code from a Git repository rather than pushing an archive from the user's local filesystem.

Users have access to the main Sample Applications interface (see the Helion Stackato User Guide), but do not have access to add new applications or store definitions.

Creating a Sample Application Store

The Sample Applications interface exposes multiple "stores" which specify the available applications. These stores are source from definition files specified in the main Settings page of the Management Console or set using kato config.

Store Definition

Store definition YAML files describe each store and its apps, including a link to the source location for each app. For example:

  title: Third Party Apps for Helion Stackato
  contact: Helion Stackato Support <>

- name: Bugzilla
  id: bugzilla
  desc: A bug tracking system for individuals or groups of developers
  framework: perl
  runtime: perl514
  services: mysql
  license: MPL
  commit: master
  mem: 256

- name: Django CMS
  id: django-cms
  desc: A content management system platform for publishing content on the internet.
  framework: python
  runtime: python27
  services: postgresql
  license: BSD
  commit: stackato
  mem: 128

- name: Node Chat
  id: node-chat
  desc: A simple chat application in Node.js with no other dependencies. Originally written by Ryan Dahl, the creator of Node.js.
  framework: node
  runtime: node
  commit: master
  mem: 64
  license: MIT

The YAML string requires two top-level keys: store and apps.


Contains entries that define the store.

Text used as a display name for Sample Applications in the Management Console.
A name and email address of the store maintainer.
An image used for the Sample Applications icon. Specified as a full URL.


This is an array of items (see YAML format above), one for each app in the store. Each app is defined by the following fields:

The name of the app as displayed in the Sample Applications list.
A short description of the app, displayed below the name.
A short, lowercase, unique string associated with the app. Apps are sorted alphabetically in the list based on this field.
URL of the git repository where the app code resides.
Branch name, tag name, or exact commit hash to use. If unspecified, the HEAD commit of master branch is used.
The framework, if the app is deployed using the Legacy Buildpack (for example, perl, python, node, rails3).
An image used for the app icon specified either as a full URL, a file relative to the store key icon-url URL, default, or other variable values.
A URL pointing to documentation for the app.
Optional string indicating the software license of the app (for example, MIT, MPL, BSD).
Memory requirements of the app (integer, in MB).
The runtime, if the app is deployed using the Legacy Buildpack (for example, java, python32, ruby19, php, perl518).
Data services required by the app.


The store definition settings do not override settings in the application's manifest.yml file.

Hosting the Store Definition Files

The YAML files defining the stores can be served via HTTP or HTTPS by any web server at a URL accessible from the Cloud Controller.

Adding Sample Applications to Helion Stackato

  1. Log into the Management Console,
  2. Select Settings > HPE Helion Stackato Settings from the menu.
  3. In the Sample Application URLs section, enter a name and content URL for your store definition YAML file then click Add Sample Application URL.

To confirm that the Sample Applications page is loading correctly, click Applications and then view the list of applications displayed. If a Sample Application URL fails to load, a CC Catalog Manager error appears in the Event Log.

Sample Application URLs can also be viewed, added, deleted, enabled, and disabled with kato config. For example:

$ kato config get cloud_controller_ng app_store