v0.2.1

Finally pulled many extension-only features into the Allay core.

Allay now supports many configuration options via config files, .allayrc, and cli

Volumes are now defined separately in .allay/volumes.yml allowing the properties: source, target and opts
In settings.yml or .allayrc, override by specifying volumes > NAME > source, target, or opts > VALUE
Via cli, override by -Vs, -Vt, or -Vo with the value of the format NAME:VALUE

Remotes are now defined separately in .allay/remotes.yml allowing the properties: active, service and ip
In settings.yml or .allayrc, override by specifying remotes > NAME > active, service, or ip > VALUE
Via cli, override by -Ra, -Rs, or -Ri with the value of format NAME:VALUE

Service activation/deactivation can be done via yml or cli by specifying services > NAME > active > yes or no or -Sa NAME:(yes or no)
Colorized and minimized output
Further output can be seen by using the -Lx options: currently -Lv (list volumes) or -Lc (list config; previously on by default) are allowed

Added extension package requirements. Extensions can now specify packages that they "require" and allay can print those requirement using the "-Le" command.

Below is a short to long option translation for all the options I've listed here:

-Vs: --allay-volume-source
-Vt: --allay-volume-target
-Vo: --allay-volume-opts
-Ra: --allay-remote-active
-Rs: --allay-remote-service
-Ri: --allay-remote-ip
-Sa: --allay-service-active
-Lv: --allay-list-volumes
-Lc: --allay-list-configuration
-Le: --allay-list-extension-requirements

v0.1.2

Settings were being incorrectly overridden by command line argument default values in v0.1.1. This release corrects the issue and allows any command line argument's value to be specified in the .allayrc or settings.yaml files.

v0.1.1

Corrected issue when merging nested data structures from settings files.

v0.1.0

Initial release allowing the configuration of docker-compose.yaml files and custom extensions to be written for Allay. So far Allay doesn't actually do anything on its own. It only provides a way to consolidate configuration files and allow them to be easily overridden without modifying version project files.