update changelog and add link in docs
All checks were successful
ci/woodpecker/push/publish-docs Pipeline was successful
All checks were successful
ci/woodpecker/push/publish-docs Pipeline was successful
This commit is contained in:
parent
02fd04930d
commit
d120c2ca8f
24
CHANGELOG.md
24
CHANGELOG.md
@ -6,6 +6,30 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
|
|||||||
and is generated by [Changie](https://github.com/miniscruff/changie).
|
and is generated by [Changie](https://github.com/miniscruff/changie).
|
||||||
|
|
||||||
|
|
||||||
|
## v0.5.0 - 2024-11-19
|
||||||
|
### Added
|
||||||
|
* Lists can now go in a file. See docs for more information.
|
||||||
|
* commands.[name].type: script now opens `scriptEnvFile`.
|
||||||
|
* Hooks for Commands.[name]. Error, success, and final. [#12]
|
||||||
|
### Changed
|
||||||
|
* GetKnownHosts is now a method of Host
|
||||||
|
### Fixed
|
||||||
|
* make command logger be used for errors, not just when running the command
|
||||||
|
|
||||||
|
## v0.4.0 - 2023-09-08
|
||||||
|
|
||||||
|
### Added
|
||||||
|
|
||||||
|
* Added `scriptEnvFile` to command object that allows one to specify an environment file (or any file really) when a `scriptFile` is run. Inspired by the practice of keeping environment variables and scripts or commands seperate.
|
||||||
|
* Basis for listing commands
|
||||||
|
|
||||||
|
### Changed
|
||||||
|
|
||||||
|
* BREAKING: Notifications object now takes the form of service.id, where service can be "mail" or "matrix" and id is a unique id for the service.
|
||||||
|
* BREAKING: Since the change to the notifications object, cmd-lists' inner map key 'notifications' must be of the form service.id. id must be defined for that service. See notifications docs for aviliable services.
|
||||||
|
* Config parser is now the simpler Koanf - Keys are now case-sensitive
|
||||||
|
* Log size limited to 50 Mb
|
||||||
|
|
||||||
## v0.3.1 - 2023-07-20
|
## v0.3.1 - 2023-07-20
|
||||||
### Changed
|
### Changed
|
||||||
* If an SSH session failed to be created, the command would fail. This would be caused when restarting the SSH host. The SSH connection is attempted to be created again. If successful, the command is executed normally.
|
* If an SSH session failed to be created, the command would fail. This would be caused when restarting the SSH host. The SSH connection is attempted to be created again. If successful, the command is executed normally.
|
||||||
|
@ -7,6 +7,8 @@ Backy is a tool for automating data backup and remote command execution. It can
|
|||||||
|
|
||||||
Why the name Backy? Because I wanted an app for backups.
|
Why the name Backy? Because I wanted an app for backups.
|
||||||
|
|
||||||
|
View the [changelog here](https://git.andrewnw.xyz/CyberShell/backy/src/branch/master/CHANGELOG.md).
|
||||||
|
|
||||||
{{% notice tip %}}
|
{{% notice tip %}}
|
||||||
Feel free to open a [PR](https://git.andrewnw.xyz/CyberShell/backy/pulls), raise an [issue](https://git.andrewnw.xyz/CyberShell/backy/issues "Open a Gitea Issue")(s), or request new feature(s).
|
Feel free to open a [PR](https://git.andrewnw.xyz/CyberShell/backy/pulls), raise an [issue](https://git.andrewnw.xyz/CyberShell/backy/issues "Open a Gitea Issue")(s), or request new feature(s).
|
||||||
{{% /notice %}}
|
{{% /notice %}}
|
||||||
|
Loading…
Reference in New Issue
Block a user