f2 VS goreleaser

An alternative solution would be to use a batch renaming tool like F2 and rename all the images based on desired variables from the existing metadata

If you want a "global" index your only choice is to rename "manually" using another tool to batch rename, that is also what I do in the moment, I just sort the files by date of creation and rename them using F2 https://github.com/ayoisaiah/f2, but you can also use Bulk Rename Utility or Advanced Renamer which is what I used to use while using windows.

250 would be no problem for the Advanced Renamer GUI. On the other hand, it really bogged down loading more than 2000 or so. And my memory was that the Advanced Renamer command-line version choked down quite badly on huge numbers of files. I wish I could remember how long the Bulk Rename Utility command-line operation took. It seemed quite reasonable to me; the critical thing for me was that I was able to process many thousands of renames in one unattended job, without having to break up the job into smaller chunks, with all the manual intervention involved. I didn't try to assign a particular number of cores for the operation. Also you might want to have a look at https://github.com/ayoisaiah/f2 .

F2 can rename based on a CSV file though if that helps

F2 is a cross-platform file renaming tool. I have to deal with a lot of incoming image files and it helps keep my file system sane.

F2 is a command-line batch renaming tool with built-in variables including date (easy to use and easy to revert if a mistake is made)

See if https://github.com/ayoisaiah/f2 helps (I haven't used it, just know about it)

I'm not sure if the labels are added to exported images, but you could then use F2 to rename the files in bulk

Read the documentation but you can use --max-depth 2 to limit it to two folders deep and use --only-dir to only rename folders

There's the awesome but difficult to google f2: https://github.com/ayoisaiah/f2 .

> This is a much faster way than setting up Github Actions to build an executable for every possible platform on every release

It's not even that hard. Just use GoReleaser.

https://goreleaser.com/

I also got my eyes on GoReleaser, which I will use in my (Go) projects.

With "xq", I went even further and automated the release process using GoReleaser. To publish a new release, the only thing I need is to create and push the Git tag. The corresponding GitHub Action will trigger a release process, and GoReleaser prepares the binaries and changelog based on declared conventions. The result has a high level of predictability, and no manual work is required.

Things I can't live without in a new Go project in no particular order:

- https://github.com/golangci/golangci-lint - meta-linter

- https://goreleaser.com - automate release workflows

- https://magefile.org - build tool that can version your tools

- https://github.com/ory/dockertest/v3 - run containers for e2e testing

- https://github.com/ecordell/optgen - generate functional options

- https://golang.org/x/tools/cmd/stringer - generate String()

- https://mvdan.cc/gofumpt - stricter gofmt

- https://github.com/stretchr/testify - test assertion library

- https://github.com/rs/zerolog - logging

- https://github.com/spf13/cobra - CLI framework

FWIW, I just lifted all the tools we use for https://github.com/authzed/spicedb

We've also written some custom linters that might be useful for other folks: https://github.com/authzed/spicedb/tree/main/tools/analyzers

Goreleaser is nice. https://goreleaser.com/

I use goreleaser for packaging my binaries. I'm not currently doing RPM, but it does a lot of services and if you don't hunker down on a single solution, it might help with keeping your releases up to date/in sync.

There's some packaging issues, for example, we've always wanted to publish deb/rpm packages, but never got around to adding it to either promu or completely switching our build tooling over to GoReleaser.