Manifest settings for web components
Overview
This reference doc details all the Manifest settings for webserver, proxy and framework components. If you’re unfamiliar with Manifest files and how they work, please follow our getting started guide and detailed how-to guide.
If you’re looking for the Manifest settings for data, caching & storage components or load balancers, please see our respective reference documents for those components.
Key to table headings
- Option - the name of the setting as used in the YAML of your Manifest file
- Applied on - the type of deployment required to update this setting. In many cases settings only apply when an application is first built, or when new servers are created or it is cloned. Hover over the names of each condition to see more info.
- Clouds - the cloud providers on which a setting can be used.
Gateway
Note
The gateway should be defined and open before you can use it in manifest.
The following settings are available via the Manifest file:
| Option | Applied on | Description | Clouds |
|---|---|---|---|
name |
Redeploy ⓘChanges to this setting will be applied when you next deploy your application |
Specify the name of gateway you want to use for your application. | All |
username |
Redeploy ⓘChanges to this setting will be applied when you next deploy your application |
Specify the username which should be used to connect to Bastion server. | All |
Example YAML for gateway
gateway:
name: aws_bastion
username: ec2-user
Nginx
Nginx is the default webserver & reverse proxy for applications managed by Cloud 66.
The following settings are available via the Manifest file:
| Option | Applied on | Description | Clouds |
|---|---|---|---|
cors |
Redeploy ⓘChanges to this setting will be applied when you next deploy your application |
Enable Cross Origin Resource Sharing | All |
perfect_forward_secrecy (deprecated) |
Redeploy ⓘChanges to this setting will be applied when you next deploy your application |
Enable Perfect Forward Secrecy | All |
Example YAML for Nginx
rails:
configuration:
nginx:
perfect_forward_secrecy: true # deprecated
CORS configuration
If required, you can also specify the allowed origin (as ‘*’ or a single origin) and methods. You can also specify a comma-separated list of origins, headers, and whether to allow credentials for CORS.
rails:
configuration:
nginx:
cors:
origin: '*'
methods: 'GET, OPTIONS'
headers: 'Custom-Header, Another-Header'
credentials: true
