chore: code grooming

Author: lukasmalkmus

.goreleaser.yaml

@@ -76,7 +76,6 @@ builds:
 archives:
   - <<: &archive_defaults
       name_template: "{{ .ProjectName }}_{{ .Version }}_{{ .Os }}_{{ .Arch }}{{ if .Arm }}v{{ .Arm }}{{ end }}"
-      rlcp: true
     id: nix
     builds:
       - darwin
@@ -125,7 +124,7 @@ brews:
     description: Syslog ingestion by proxy for Axiom
     homepage: https://axiom.co
     license: MIT
-    tap:
+    repository:
       owner: axiomhq
       name: homebrew-tap
       token: "{{ .Env.HOMEBREW_TOKEN }}"

README.md

@@ -30,6 +30,11 @@ For more information check out the
 
 ## Usage
 
+💡 _Setting up `axiom-syslog-proxy` for secure syslog? Think about using
+[an endpoint](https://axiom.co/docs/endpoints/introduction)! You can create one
+by visiting
+[the Axiom endpoint settings](https://app.axiom.co/vercel-pbue/settings/endpoints)._
+
 There are multiple ways you can install the Axiom Syslog Proxy:
 
 - With Homebrew: `brew install axiomhq/tap/axiom-syslog-proxy`
@@ -43,9 +48,16 @@ There are multiple ways you can install the Axiom Syslog Proxy:
 If you use the [Axiom CLI](https://github.com/axiomhq/cli), run
 `eval $(axiom config export -f)` to configure your environment variables.
 
-Otherwise create a personal token in [the Axiom settings](https://app.axiom.co/profile)
-and export it as `AXIOM_TOKEN`. Set `AXIOM_ORG_ID` to the organization ID from
-the settings page of the organization you want to access.
+Otherwise create an api token with the appropriate scopes in
+[the Axiom API tokens settings](https://app.axiom.co/settings/api-tokens) and
+export it as `AXIOM_TOKEN`.
+
+When using a personal token, export it as `AXIOM_TOKEN` and set `AXIOM_ORG_ID`
+to the organization ID from the settings page of the organization you want to
+access.
+
+_❗ We recommend to follow security best-practices and use an **api token with
+minimal privileges**, only!_
 
 Export the dataset name to ingest into as `AXIOM_DATASET`. The dataset must
 exist prior to ingesting data into it.