https://github.com/infogulch/xtemplate/blob/master/make_tool.cue

[gedw99]

very cool @infogulch

Will have a play :)

I was looking at using Cue too. Benthos also uses Cue for this.

[gedw99]

Had a look at your Cue. It's verbose and requires a compile.

But I think you can also do Cue without needing a Compile step too.

I have been using Task, which I am sure you know too.

https://github.com/go-task/task
https://taskfile.dev

[infogulch]

Not sure what you mean by "requires a compile step". You need cue installed but it should just work.

I mainly did this as an experiment to see if cue tool files could be suitable as a replacement for makefiles. I have a list of annoyances that I ran into during the process and I'll probably write it up into something digestible and publish it for the cue team, but in short I'd say the experiment was a mixed success. It's a bit complicated, but it does a lot:

• runs go tests
• builds and runs xtemplate integration tests in 3 formats on linux:
  • Caddy+xtemplate
  • xtemplate binary
  • xtemplate Docker image
• cross-compiles and packages xtemplate binary with overridden version flag matching the current git tag, with all current providers, and sqlite3 for 3 platforms:
  • linux
  • mac
  • windows
• tags and publishes docker image
• does all of this in parallel as much as possible
• allows you to execute any of the above tasks or commands individually, e.g.:
  • build and run xtemplate: cue cmd run
  • execute tests against running xtemplate instance: cue cmd test
  • build and test and stop: cue cmd build_test
  • everything: cue cmd ci
  • etc

I'm not sure but I think that's a fairly good result for 230 LoC.

[gedw99]

Not sure what you mean by "requires a compile step". You need cue installed but it should just work.

I mainly did this as an experiment to see if cue tool files could be suitable as a replacement for makefiles. I have a list of annoyances that I ran into during the process and I'll probably write it up into something digestible and publish it for the cue team, but in short I'd say the experiment was a mixed success. It's a bit complicated, but it does a lot:

• runs go tests

• builds and runs xtemplate integration tests in 3 formats on linux:

  • Caddy+xtemplate
  • xtemplate binary
  • xtemplate Docker image

• cross-compiles and packages xtemplate binary with overridden version flag matching the current git tag, with all current providers, and sqlite3 for 3 platforms:

  • linux
  • mac
  • windows

• tags and publishes docker image

• does all of this in parallel as much as possible

• allows you to execute any of the above tasks or commands individually, e.g.:

  • build and run xtemplate: cue cmd run
  • execute tests against running xtemplate instance: cue cmd test
  • build and test and stop: cue cmd build_test
  • everything: cue cmd ci
  • etc

I'm not sure but I think that's a fairly good result for 230 LoC.

You can do ALL of these things in a task file.

here is a nice example: https://github.com/starfederation/datastar/blob/develop/Taskfile.yml

I love Cue but its more for much more complex configuration thing if you ask me.

Task also has 2 GUI for Task. One is a TUI and the other is a Web GUI. It's mature and wildly popular.

give it a try.