2 ms·
Regardless of the language I use for a project I always have these: - make test - make build (or run if it's an interactive app) - make publish Publish
by theshrike79 5y ago
Regardless of the language I use for a project I always have these:
- make test
- make build (or run if it's an interactive app)
- make publish
Publish runs test + build and uploads it to "production".
For Go projects I've started to move to Magefiles though: https://magefile.org https://magefile.org
- dgsb 5y agomage is great, I'm moving forward to that too.
- sigmonsays 5y agoI dont get mage, but i've been using makefiles for over 13 years. I love go but the only example on the site is bad, and there is not any others. Also, executing commands in go is tedious and verbose w/o helpers. The "Why" on the page fails to convince me as well. How is a makefile too much whitespace? Is there any good examples of mage being used in a larger project? preferably a popular one?
- theshrike79 5y agoIf your makefile is mostly just simple single commands, there really is no point in moving to magefiles. The test/lint/build phases of my magefiles are mostly the same as makefiles. What differs is the publish command: There I can make use of (for example)native AWS libraries to do complex deployment processes with error checking and validation. All this is of course doable with makefiles, but it gets very tedious compared to a "real" programming language.