Skip to content

v0.2.1

Latest
Compare
Choose a tag to compare
@brian-dlee brian-dlee released this 20 Sep 21:56
· 5 commits to release/v0.2 since this release

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