![]() If all that is right, then you put this file in your project root as "Makefile" and your package.json "start" script would then be "make start". The important bit here is that the file must be called "Makefile". That leads me to believe that if there is a "Makefile" in a directory, then you execute "make sometarget" and the target inside "Makefile" will be executed. That said, I did find an example discussing use of "Phony" targets which provided enough detail for me to infer that a "Makefile" with a "phony" target of "clean" would be executed with "make clean". I'm not 100% sure there and in any case, I can't find a clear and simple example of how to use the targets which seems pretty silly since they're clearly a CORE part of this concept. ![]() You could just as easily name this file "MyApp" then execute "make MyApp" and it would do the same from what I can tell. If this file exists in a directory by the name "Makefile", then you can execute "make" by itself and if the make utility is installed, it will look at your working directory for "Makefile" and execute it. That said, I started Googling and quick figured out that "start", "stop", "restart", etc. I'm a fan of forever, trying to figure out clustering and at the moment deploying to modulus.io, but preparing for a move to AWS and I've never implemented a MakeFile myself despite having worked with them in compiling others' code for > 15 years :)
0 Comments
Leave a Reply. |