kada/README.md

Kada

This is a rewrite of abra, as it is the next part of abrakadabra, the next tool will be called bra then... I like the idea of abra, more specifically, coop-cloud, to have a collaborative way of developing and maintaining recipes for open-source services. kada uses the recipes provided by abra, but puts another layer on top of them. Here is how I want kada to behave:

• configuration
  • kada is written to be used in multiple directories and does not rely on the ~/.abra directory
  • kada can also be used directly in a recipe directory to work on a recipe
  • allow configuration of preferences for your installation
• recipe catalogues - use the coop-cloud catalogue by default, but allow adding other catalogues
• kada directory
  • servers/[domain] for every server
    • [subdomain]/ each subdomain/app has its own directory
      • config.yaml holds the configuration, which is based on the .env files provided by abra
      • recipe/ is an optional directory for local recipes - if it is present, it overrides the recipe in the config.yaml file, but needs a --chaos flag
  • .recipes/ for a cache of locally recipes - one directory per recipe/version pair
• kada

Config.yaml

• recipe configuration
  • .env files versioning - use a config-file instead of .env files, so that additions to the .env file can be represented in the config file

Upgrading a recipe

Testing recipe upgrade