Helion Stackato exposes a number of predefined environment variables during runtime (including hook processing, cron jobs and ssh commands).
You can set your own environment variables:
env:block in manifest.yml
To see a complete list of environment variables in a Helion Stackato application container, deploy the node-env sample.
Contains an access URL for a database service. If more than one type
of database is present,
DATABASE_URL will not be available.
Instead, use the Database Specific URL variables below. Example:
:, which are to be searched for the names of executable files to be interpreted as commands.
Custom/alternate PIP repo location. For example:
env: PIP_OPTS: "--extra-index-url=http://company.com/inhouse-pypi-mirror"
This variable contains the default start command that would be used when manifest.yml does not override it. It is provided so that users can specify a wrapper around the default command. For example:
processes: web: newrelic_wrapper $PROCESSES_WEB
PROCESSES_WEB may be undefined when Helion Stackato cannot determine the
default command (for example, because the app uses a non-standard main application file).
Custom/alternate PyPM repo location. Repo mirroring is sort of undocumented feature. Example:
env: PYPM_OPTS: "-R http://pypm-free.activestate.com/2.7/linux-x86_64/"
Internal use, subject to change.
manifest.yml). Available during staging as well as in the application instance.
Contains the same value as
STACKATO_APP_NAME transformed to
uppercase, with dashes replaced by underscores. For example if
This is the
root directory from the Helion Stackato point of view.
It contains app specific
HOME directory (
app/), the log file directory
logs/) and various scripts.
The HOME environment variable actually points to the app directory,
which commonly looks like the directory uploaded by the client. This is where
manifest.yml and all the application files are located.
If the app uses a single
filesystem service, then the local
mount point is stored in this variable.
If there is more than one
STACKATO_FILESYSTEM is not available.
Instead, a custom environment variable
STACKATO_FILESYSTEM_* will be created based on the
name of each filesystem service (with hyphens replaced by underscores).
For example, if your
manifest.yml file configures the following services:
services: my-data: filesystem plugins: filesystem
Two environment variables would be created:
This variable is deprecated. It can be used only with Stackato 2.x.
Can be set in the local shell to specify the group
stackato client. When set, the
command is ignored until the variable is explicitly unset. If empty,
the client sets the group to
none. Can be overridden with the
stackatoclient. When set, the
stackato targetcommand is ignored until the variable is explicitly unset. Can be overridden with the
Set by the Perl and Python frameworks only. It contains the default UWSGI start command to run the application via uwsgi. It is provided in case the user wants to add additional uwsgi options in manifest.yml:
processes: web: $STACKATO_UWSGI --another-uwsgi-option
The following environment variables are available during application staging, and can be used in buildpacks or staging hooks:
BUILDPACK_CACHE: Filesystem location the buildpack uses to store assets during the build.
https_proxy: The proxy host:port of the DEA running the staging container.
STAGING_TIMEOUT: Time limit for staging to complete.
USER: Will always be "stackato"
Service instance variables (for example,
can change between staging and running. Do not save values from these
variables to config files during staging as the hard-coded values may
no longer be applicable after staging.