diff --git a/.github/workflows/cd.yml b/.github/workflows/cd.yml index 66e71608..10c99e43 100644 --- a/.github/workflows/cd.yml +++ b/.github/workflows/cd.yml @@ -10,15 +10,15 @@ jobs: runs-on: ubuntu-latest steps: - name: Checkout code - uses: actions/checkout@v2 + uses: actions/checkout@v4 - name: Unshallow repo run: git fetch --prune --unshallow - name: Setup Go - uses: actions/setup-go@v1 + uses: actions/setup-go@v4 with: go-version: 1.21.x - name: Run goreleaser - uses: goreleaser/goreleaser-action@v1 + uses: goreleaser/goreleaser-action@v5 with: distribution: goreleaser version: v1.17.2 diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index b9461e75..b90b7b91 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -23,13 +23,13 @@ jobs: GOFLAGS: -mod=vendor steps: - name: Checkout code - uses: actions/checkout@v2 + uses: actions/checkout@v4 - name: Setup Go - uses: actions/setup-go@v1 + uses: actions/setup-go@v4 with: go-version: 1.21.x - name: Cache build - uses: actions/cache@v1 + uses: actions/cache@v4 with: path: ~/.cache/go-build key: ${{runner.os}}-go-${{hashFiles('**/go.sum')}}-test @@ -45,13 +45,13 @@ jobs: GOARCH: amd64 steps: - name: Checkout code - uses: actions/checkout@v2 + uses: actions/checkout@v4 - name: Setup Go - uses: actions/setup-go@v1 + uses: actions/setup-go@v4 with: go-version: 1.21.x - name: Cache build - uses: actions/cache@v1 + uses: actions/cache@v4 with: path: ~/.cache/go-build key: ${{runner.os}}-go-${{hashFiles('**/go.sum')}}-build @@ -73,13 +73,13 @@ jobs: GOARCH: amd64 steps: - name: Checkout code - uses: actions/checkout@v2 + uses: actions/checkout@v4 - name: Setup Go - uses: actions/setup-go@v1 + uses: actions/setup-go@v4 with: go-version: 1.21.x - name: Cache build - uses: actions/cache@v1 + uses: actions/cache@v4 with: path: | ~/.cache/go-build @@ -100,13 +100,13 @@ jobs: GOFLAGS: -mod=vendor steps: - name: Checkout code - uses: actions/checkout@v2 + uses: actions/checkout@v4 - name: Setup Go - uses: actions/setup-go@v1 + uses: actions/setup-go@v4 with: go-version: 1.21.x - name: Cache build - uses: actions/cache@v1 + uses: actions/cache@v4 with: path: ~/.cache/go-build key: ${{runner.os}}-go-${{hashFiles('**/go.sum')}}-test diff --git a/.github/workflows/sponsors.yml b/.github/workflows/sponsors.yml index cda2fce4..81a200c9 100644 --- a/.github/workflows/sponsors.yml +++ b/.github/workflows/sponsors.yml @@ -9,7 +9,7 @@ jobs: runs-on: ubuntu-latest steps: - name: Checkout 🛎️ - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Generate Sponsors 💖 uses: JamesIves/github-sponsors-readme-action@v1.2.2 diff --git a/.golangci.yml b/.golangci.yml index f1fcc4c1..1d325e3a 100644 --- a/.golangci.yml +++ b/.golangci.yml @@ -1,13 +1,11 @@ linters: - disable: - - structcheck # gives false positives enable: - gofumpt - thelper - goimports - tparallel - wastedassign - - exportloopref + - copyloopvar - unparam - prealloc - unconvert diff --git a/README.md b/README.md index 0af77059..2bb85986 100644 --- a/README.md +++ b/README.md @@ -1,29 +1,3 @@ -
-
- Maintenance of this project is made possible by all the contributors and sponsors. If you'd like to sponsor this project and have your avatar or company logo appear below click here. 💙 -
- - - ## Elevator Pitch Minor rant incoming: Something's not working? Maybe a service is down. `docker-compose ps`. Yep, it's that microservice that's still buggy. No issue, I'll just restart it: `docker-compose restart`. Okay now let's try again. Oh wait the issue is still there. Hmm. `docker-compose ps`. Right so the service must have just stopped immediately after starting. I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services. I could get the logs for just that one service with `docker compose logs --follow myservice` but that dies everytime the service dies so I'd need to run that command every time I restart the service. I could alternatively run `docker-compose up myservice` and in that terminal window if the service is down I could just `up` it again, but now I've got one service hogging a terminal window even after I no longer care about its logs. I guess when I want to reclaim the terminal realestate I can do `ctrl+P,Q`, but... wait, that's not working for some reason. Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service. diff --git a/assets/subble.webp b/assets/subble.webp new file mode 100644 index 00000000..7b460ac6 Binary files /dev/null and b/assets/subble.webp differ diff --git a/assets/tuple.png b/assets/tuple.png new file mode 100644 index 00000000..1d7be47c Binary files /dev/null and b/assets/tuple.png differ diff --git a/assets/warp.png b/assets/warp.png deleted file mode 100644 index 1422f11c..00000000 Binary files a/assets/warp.png and /dev/null differ diff --git a/assets/warp2.png b/assets/warp2.png new file mode 100644 index 00000000..faf1ed5e Binary files /dev/null and b/assets/warp2.png differ