Static env files

[brickpop]

• Use the makefile to automatically pick the right values to feed
• Avoid editing config files during the deployment process
• Reusing common commands
• Storing deployment logs into a file
• Reactive makefile targets
  • Removing coverage.sh, doing the work on make instead
• Make env values general purpose
• Add an auto generated make help target
• Improve the make init target

[jordaniza]

I think these are really nice changes, thank you. Cleaning up and productionising the makefile and segmenting the tests is excellent.

There's a slight extra overhead having to learn the makefile syntax which I wasn't intimately familiar with, but piping it through GPT it became pretty clear. I would expect most users just use the default commands in the readme.

[jordaniza]

It's a bit confusing that this env var isn't defined in any .env file but I can see later where this gets injected.

[brickpop]

Fair point @jordaniza. Since the developer experience is about using the makefile (rather than tweaking it), we can maybe reference the related targets (make test-exfork-testnet, ...) instead of naming the env var?

[jordaniza]

Again, I can see what you're doing here having all the instantiation of env vars in the same place - was jumping around a bit to follow the make dependencies but now I get it - maybe we move them next to each other?

[brickpop]

Done 👍
I have left only 3 at the top, because they might need to be changed and I think it's good that they remain easy to spot.

[jordaniza]

I think w/o a comment it's kinda confusing why these particular filenames are here.

[brickpop]

Does it work with a name like TEST_COVERAGE_SRC_FILES?

[brickpop]

I think these are really nice changes, thank you. Cleaning up and productionising the makefile and segmenting the tests is excellent.

There's a slight extra overhead having to learn the makefile syntax which I wasn't intimately familiar with, but piping it through GPT it became pretty clear. I would expect most users just use the default commands in the readme.

The main goal would be to just 'use' the makefile rather than needing to read/edit it, but for the sake of the review it obviously needs to be clear :)

Among the idiomatic makefile details to remark, I should probably have mention:

• The use of inheritable env vars (make the final commands work on any scenario)
• Defining build rules in a declarative fashion, rather than imperative
  • Linking artifacts to the source files that generate them

Is this what needed a bit of clarification?