Skip to content

Commit

Permalink
0.1.4
Browse files Browse the repository at this point in the history
  • Loading branch information
maksimryndin committed Mar 1, 2024
1 parent b6e54de commit 196de1a
Show file tree
Hide file tree
Showing 5 changed files with 17 additions and 13 deletions.
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/BUG_REPORT.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,7 @@ body:
label: Which version of Goral do you run (`goral --version`)?
multiple: false
options:
- 0.1.4
- 0.1.3
- 0.1.2
- 0.1.1
Expand Down
2 changes: 1 addition & 1 deletion .github/site/src/install.sh
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ main() {

get_architecture || return 1
local _arch="$RETVAL"
local _version=${1:-'0.1.3'}
local _version=${1:-'0.1.4'}
assert_nz "$_arch" "arch"

local _file="goral-${_version}-${_arch}"
Expand Down
4 changes: 2 additions & 2 deletions .github/site/src/recommended-deployment.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,5 @@
# Recommended deployment

## Linux

Goral follows a fail-fast approach - if something violates assumptions (marked with `assert:`), the safest thing is to panic and restart. It doesn't behave like that for recoverable errors, of course. For example, if Goral cannot send a message via messenger, it will try to message via General service notifications and its logs. And will continue working and collecting data. If it cannot connect to Google API, it will retry first.

For some services like healthcheck you may want to suppress sending of Google API errors with
Expand All @@ -14,6 +12,8 @@ to minimize unactionable notifications. Failure to append rows to a spreadsheet

There is also a case of fatal errors (e.g. `MissingToken error` for Google API which usually means that system time has skewed). In that case only someone outside can help. And in case of such panics Goral first tries to notify you via a messenger configured for General service to let you know immediately.

## Linux

So following Erlang's idea of [supervision trees](https://adoptingerlang.org/docs/development/supervision_trees/) we recommend to run Goral as a systemd service under Linux for automatic restarts in case of panics and other issues.

1. [Install](./installation.md) Goral
Expand Down
19 changes: 9 additions & 10 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -91,16 +91,15 @@ jobs:
run: |
cargo clippy -- -D warnings
# TODO uncomment when cargo deny will fix a dependency issue
# - name: Install audit
# shell: bash
# run: |
# cargo install cargo-deny

# - name: Security audit, licenses
# shell: bash
# run: |
# cargo deny check licenses advisories sources
- name: Install audit
shell: bash
run: |
cargo install cargo-deny
- name: Security audit, licenses
shell: bash
run: |
cargo deny check licenses advisories sources
- name: Test
shell: bash
Expand Down
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,7 @@
* 0.1.4
* minor improvements for notifications
* urls with specified domains do not require ports

* 0.1.3
* fix version message for telegram
* releases for other platforms
Expand Down

0 comments on commit 196de1a

Please sign in to comment.