A stupid simple make wrapper that makes my life easier

• cake

  3 144 0.0 Shell

  A sweet make wrapper 🍰 (by cyruseuros)

• Cake

  13 3,818 8.2 C#

  :cake: Cake (C# Make) is a cross platform build automation system.

  

Looks interesting! Although the name clashes with Cake (C# Make) project which could be confusing - https://cakebuild.net/

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• doit

  20 1,781 0.0 Python

  task management & automation tool

  

• run

  17 473 3.5 Go

  Task runner that helps you easily manage and invoke small scripts and wrappers (by TekWizely)

> why not just do a bash script with a switch in it?

Here is another alternative:

https://github.com/TekWizely/run

• web-security-map

  2 - -

Take a look at one of my Makefiles[0]. It uses most features Make has to offer (to much so). It doesn't matter what state you start from, fresh clones repo or outdated virtualenv. Running `make run` will do everything needed to run the application instance, `make test` will run the testsuite. Each command is it's own "functional" block of shell script with it's inputs (prerequisites) and outputs (target). All recipies will run in Bash on all system btw, see the first line of the Makefile.

Still, a Makefile with only targets, no prerequisites is less cruft than a Bash script with a switch statement. But eventually your (team) needs will grow and you start to introduce more logic and dependencies. This is where Make shines for me.

[0] https://gitlab.com/internet-cleanup-foundation/web-security-...

• web-security-

  2 - -

Take a look at one of my Makefiles[0]. It uses most features Make has to offer (to much so). It doesn't matter what state you start from, fresh clones repo or outdated virtualenv. Running `make run` will do everything needed to run the application instance, `make test` will run the testsuite. Each command is it's own "functional" block of shell script with it's inputs (prerequisites) and outputs (target). All recipies will run in Bash on all system btw, see the first line of the Makefile.

Still, a Makefile with only targets, no prerequisites is less cruft than a Bash script with a switch statement. But eventually your (team) needs will grow and you start to introduce more logic and dependencies. This is where Make shines for me.

[0] https://gitlab.com/internet-cleanup-foundation/web-security-...

Suggest a related project