[datastack]

some tasks a developer might need to do besides just building the application:

- copying a database from production to local for bug reproduction/fixes - inserting seed-data into the local database - creating a migration after changing records - applying the migration - rolling back the migration - running a tool to copy configuration from a keyvault - running the end to end tests - generate certificates - set up an ssh tunnel to a remote server or database

All of these things are part of the development process, and cannot be part of the build system. Each of them has their own commands and tools.

All developers need to easily be able to do these things, without asking help each time, or learning the syntax of each command.

One easy way is to stuff all of them in a task runner with simple aliases. Another could be writing a document that you can copy/paste from. I prefer a task runner, since you can memorize the alias and work from the terminal without looking things up.

[crabbone]

So, what's your point exactly? There are plenty of tools for this that do it a lot better than Taskfile? Like, Ansible for example?

Also, what makes you think a build system doesn't or shouldn't do those things?

Also, you could just write a Shell script to do all of those -- what's the difference?

[inopinatus]

> stuff all of them in a task runner with simple aliases

$ mkdir bin

> easily be able to do these things, without asking help each time

$ ls bin

> generate certificates

$ bin/mkcert.sh

What you didn't need: yet another tool and config syntax as a dumping bucket for your one-liners and command aliases.