Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev Env / CI #41

Open
LAV42 opened this issue Aug 29, 2024 · 0 comments
Open

Dev Env / CI #41

LAV42 opened this issue Aug 29, 2024 · 0 comments

Comments

@LAV42
Copy link

LAV42 commented Aug 29, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant