Issue: When setting up a new package for auto-install, Muddler:new doesn't throw an error or debug message for missing file.
Expected behaviour,
When you add the following script to mudlet scripts:
myCIhelper = myCIhelper or Muddler:new({
path = "/home/<user>/<path>/<to>/<project_root>/"
})
It should minimally echo something to tell you it couldn't find .../build/<something>.mpackage
(In the first place I thought I had done something wrong in my setup when it was a typo)
Comment:
For people on-boarding, I believe it would be simpler to have muddle --generate-dev to ship with the muddler.mpackage lua code. You then install your barebone package, and it updates on the fly. The docker muddle can do pwd and figure out where we are on host machine to prepare the right script and put it in the scripts/ directory. Just my 2 cents.
Issue: When setting up a new package for auto-install,
Muddler:newdoesn't throw an error or debug message for missing file.Expected behaviour, When you add the following script to mudlet scripts:
It should minimally
echosomething to tell you it couldn't find.../build/<something>.mpackage(In the first place I thought I had done something wrong in my setup when it was a typo)
Comment: For people on-boarding, I believe it would be simpler to have
muddle --generate-devto ship with themuddler.mpackagelua code. You then install your barebone package, and it updates on the fly. The dockermuddlecan dopwdand figure out where we are on host machine to prepare the right script and put it in thescripts/directory. Just my 2 cents.