WARNING: These APIs are currently in an 'alpha' state and are likely to change over time. We recommend you not use them in a production setting at this time!
DataElements are building blocks. When you want to make your application do something, these building blocks are added to a
Library is built into a
Build. The exact contents of the
Build depend upon the
Environment settings and the resources included in the
Library. Specifically, the
- Destination - This is the location where you want your build to be deployed. It is controlled by selecting an
Adapter for the environment to use
- Archive - You can get a deployable set of files or have it zipped up in an archive format. This is controlled by the archive setting on the
The combination of destination and archive format will change how you reference the
Build that Launch produces (that reference is often called an embed code). If you make any changes to destination or file format, you’ll need to make a matching update to your application to use the new reference.
You’ll need to create an
Adapter before you can create an
Environments come in three types or
stages and you can create the specified number of each:
Environment types have similar behavior, but are used at different stages of the publishing workflow in Launch.
Environment belongs to exactly one
Property can have one
stage = 'production', one
stage = 'staging', and many
stage = 'Development' .
You can read more about environments in the Environments section of the Launch user docs.