#I have questions on the relationship

1 messages · Page 1 of 1 (latest)

warm nimbus
#

My rough definitions:

  • A project is a directory where I "do cloak stuff". It has a cloak.yaml, and possible some source code for custom extensions.
  • An extension is a special piece of code which can cloak can load to extend what its API can do. APIs are built from a source directory (which currently requires a Dockerfile) and are given a name when loaded
#

The relationships I see at the moment:

  • A project is collection of extensions. The project's config file (cloak.yaml) specifies how to build each extension, and what name to load it as.
  • A project may combine extensions built from the project directory (ie. todoapp extension is part of todoapp project), or extensions built from an external source (ie netlify, alpine). But cloak doesn't make a distinction between the two. They are mixed and matched seamlessly