github.com/dahs81/otto@v0.2.1-0.20160126165905-6400716cf085/website/source/docs/apps/custom/dev.html.md (about)

     1  ---
     2  layout: "app_custom"
     3  page_title: "Development - Custom App Type"
     4  sidebar_current: "docs-custom-dev"
     5  description: |-
     6    "Custom" application types use Vagrant for development.
     7  ---
     8  
     9  # Development
    10  
    11  "Custom" application type development environments are defined by
    12  a "dev" [customization](/docs/apps/custom/customization.html) and use
    13  Vagrant.
    14  
    15  -> **NOTE:** This page documents the "custom" application type. Theres are
    16     different from [application type plugins](/docs/plugins/app.html) which
    17     are a way to introduce new application types to Otto.
    18  
    19  ## Example
    20  
    21  ```
    22  application {
    23      name = "my-app"
    24      type = "custom"
    25  }
    26  
    27  customization "dev" {
    28      vagrantfile = "./Vagrantfile"
    29  }
    30  ```
    31  
    32  For the Appfile above, running `otto dev` will run Vagrant in the directory
    33  of the Appfile against the given Vagrantfile.
    34  
    35  The Vagrantfile is rendered as [a template](/docs/apps/custom/template.html).
    36  It is important at the very least to specify the Vagrant shared folder
    37  should be the working directory. An example Vagrantfile config is shown
    38  below to do this:
    39  
    40  ```
    41  config.vm.synced_folder '{{ path.working }}', "/vagrant"
    42  ```
    43  
    44  If you don't do this, then the directory that `/vagrant` sees will be
    45  the compiled directory, which is very likely not what you want.