> I built Ledge because I spend much of my day copy/pasting commands from my notes into the terminal. I was inspired by how much cmux helped me organize my terminals - but there was still a split brain between my notes and frequently Run commands. I've been daily-driving it for the past few weeks and use it for deploys, API calls, smoke tests, etc.
I see it might be handy for exploring your own pipelines (and so are things like <a href="https://github.com/akavel/up/" rel="nofollow">https://github.com/akavel/up/ ) , but I advise against using this for any serious project management. Nontrivial and/or crucial code-blocks in markdown files is an anti-pattern.
Once i find I'm re-using code from my markdown notes, I make it a script in ${dotfiles}/bin or in ${project}/scripts and put related docs in there. This feels like the inverse of this tool's imposed workflow and has the upside of composability of tools.
Then use something like a makefile to call these tools/scripts behind generic phony targets (or you can roll your own 'project.sh' entry point script if really needed).
It then becomes just `make release`. it is portable already and does not add yet another host dependency on everybody nor a fricking javascript engine.
ps1: Same goes for weird stuff like <a href="https://pypi.org/project/taskipy/" rel="nofollow">https://pypi.org/project/taskipy/ . use `make release` over `poetry run task release`
ps2: if you're copy/pasting-workflow sucks: improve it. vim has :Terminal, it has yank-to-clipoard etc.
Ledge doesn't remove the need to write scripts / automations. But for things like complex deploy pipelines there are still many manual / human steps in between. So I use Ledge to run my automation scripts, do some manual checks, based on those run more automations, etc.
Piraty · · focus · HN ↗
I see it might be handy for exploring your own pipelines (and so are things like <a href="https://github.com/akavel/up/" rel="nofollow">https://github.com/akavel/up/ ) , but I advise against using this for any serious project management. Nontrivial and/or crucial code-blocks in markdown files is an anti-pattern.
Once i find I'm re-using code from my markdown notes, I make it a script in ${dotfiles}/bin or in ${project}/scripts and put related docs in there. This feels like the inverse of this tool's imposed workflow and has the upside of composability of tools.
Then use something like a makefile to call these tools/scripts behind generic phony targets (or you can roll your own 'project.sh' entry point script if really needed). It then becomes just `make release`. it is portable already and does not add yet another host dependency on everybody nor a fricking javascript engine.
ps1: Same goes for weird stuff like <a href="https://pypi.org/project/taskipy/" rel="nofollow">https://pypi.org/project/taskipy/ . use `make release` over `poetry run task release`
ps2: if you're copy/pasting-workflow sucks: improve it. vim has :Terminal, it has yank-to-clipoard etc.
dancablam · · focus · HN ↗