You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently you have to clone repositories and install and hope that all these (apparently, a bit fragile) setup-scripts do their job.
It would be grate if you could just create an directory full with your definitions and run npx esqlate --user .... and be up and running. From an technical standpoint that should be fairly doable by including a "bin" section into the package.json.
The UX would be top notch and would serve to solve the problem mentioned in the readme ("You’re taking time away from developers / systems administrators to do things which could, sometimes, be done by less technical employees.").
Let me know what you think about this :) Cheers
The text was updated successfully, but these errors were encountered:
I'm pretty dissatisfied with the desktop method and unsure on whether it should be at all.
I never did think about the NPX method and I think you might be right that that will be a better way to go.
I do have other wild ideas / partial implementation about how to do something which achieves the same aim, it's just taking far longer than I would have hoped.
Would be happy to have contributions on this though.
I don't have extra capacity to contribute atm, sadly but if I can help by answering questions, feel free ;)
One example repository where I used the npx-way for reference: https://github.com/phuhl/apparts-s3deploy
In there, there are actually two npm packages, don't get fooled by that, the important part is just the "bin" in the package.json's that point to an executable js file (with #! at the start, I think).
Currently you have to clone repositories and install and hope that all these (apparently, a bit fragile) setup-scripts do their job.
It would be grate if you could just create an directory full with your definitions and run
npx esqlate --user ....
and be up and running. From an technical standpoint that should be fairly doable by including a "bin" section into the package.json.The UX would be top notch and would serve to solve the problem mentioned in the readme ("You’re taking time away from developers / systems administrators to do things which could, sometimes, be done by less technical employees.").
Let me know what you think about this :) Cheers
The text was updated successfully, but these errors were encountered: