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

     1  ---
     2  layout: "docs"
     3  page_title: "Plugins - Appfile"
     4  sidebar_current: "docs-plugins"
     5  description: |-
     6    Otto was architected around a plugin-based architecture. All
     7    application types and infrastructure types
     8    are plugins, even the core built-in types.
     9  ---
    10  
    11  # Plugins
    12  
    13  Otto was architected around a plugin-based architecture. All
    14  [application types](/docs/apps) and [infrastructure types](/docs/infra)
    15  are plugins, even the core built-in types.
    16  
    17  This section of the documentation gives a high-level overview of how to write
    18  plugins for Otto. It does not hold your hand through the process, however, and
    19  expects a relatively high level of understanding of Go, Otto semantics,
    20  Unix, etc.
    21  
    22  Plugins were introduced in Otto 0.2. If you're using an earlier version of
    23  Otto, plugins will not work. From Otto 0.2 onwards, any available plugins
    24  can be used. If a plugin isn't compatible with your version of Otto, Otto
    25  will give you a nice error message.
    26  
    27  If you're only interested in using plugins, see the
    28  [plugin installation](/docs/plugins/install.html) page. If you're interested
    29  in developing plugins, see the [development basics](/docs/plugins/basics.html)
    30  page.
    31  
    32  ~> **Advanced topic!** Plugin development is a highly advanced topic in
    33     Otto, and is not required knowledge for day-to-day usage. If you don't plan
    34     on writing any plugins, we recommend not reading this section of the
    35     documentation.