Getting Started with Manifest

Manifest Tutorial

In this example we are going to modify the configuration of the simple application we used in our Getting started guide.

Updating the Manifest file

node:
  configuration:
    custom_log_files: ["/tmp/mylog/*/*.log"]

You'll see that we're defining several things in this YAML:

• The framework we are configuring (node)
• The location of our custom log files ( ["/tmp/mylog/*/*.log"])

Next, deploy your application and the new setting will take effect!

Defining a server for your component

The Manifest file gives you a lot of control over your components. For example, you can use the server settings to specify the exact size and region for your application server. The YAML below is an example of this in action:

node:
  configuration:
    custom_log_files: ["/tmp/mylog/*/*.log"]
  servers:
  - server:
      unique_name: master
      size: s-2vcpu-2gb
      region: lon1
      vendor: digitalocean
      key_name: My_DO_Account # the name of your cloud provider in your Cloud 66 account

This would install your Node application on DigitalOcean, at their London data centre and on a 2CPU and 2GB cloud server.

• You can find the available values for size and region in our API documentation.
• You can find the key_name for your cloud provider(s) listed on your Dashboard.