Version
- Getting started
- Overview
- Installation
- Quickstart
- Upgrading
- Setting up your pipeline
- Determining needs
- Using Plugins
- Deploying your app
- Plugin Packs
- Authoring Plugins
- Creating a plugin
- Pipeline hooks
- The deployment context
- Creating a plugin pack
- Creating in-repo plugins
- Cookbook
- Default options
- Using .env for secrets
- Including a plugin twice
- Development workflow
- The lightning strategy
- S3 walkthrough
- Deploy non-Ember apps
- Reference
- Usage
- Configuration
- Other API/Classes
Improve this page
Including a plugin twice
Often it is necessary to invoke an instance of a plugin more than once, for instance using the s3 plugin to push assets to two different buckets.
We can do this by using the pipeline.alias config option, like so:
var ENV = {
pipeline: {
alias: {
s3: { as: ['s3-eu', 's3-us'] },
},
},
};
This configuration will then allow you to set different configuration options for the two instances of the s3 plugin, referenced by their alias names, like so:
var ENV = {
pipeline: {
alias: {
s3: { as: ['s3-eu', 's3-us'] },
},
},
's3-eu': {
bucket: 'bucket-1',
},
's3-us': {
bucket: 'bucket-2',
},
};
You can pass either a string or an array of strings in as the alias value like so:
var ENV = {
pipeline: {
alias: {
s3: { as: ['s3-eu', 's3-us'] },
redis: { as: 'redis-local' },
},
},
};