dancablam
Joined 14 years ago
Joined 14 years ago
And, dang - sorry it's laggy for you! I've created a GH issue that includes some things for you to try and I'll work through them myself too: https://github.com/ledgesh/ledge/issues/8
1. Ledge's bet is it shouldn't feel like authoring at all. I've always had markdown docs chock full of commands and docs so making them runnable was the next logical step for me.
2. True. Keeping any kind of documentation up to date is difficult
3. Also true. I'm hoping Ledge's built-in agent support will bridge that gap and allow agents to help keep the docs up-to-date
And yes, a "Team" notebook is a challenge. Technically anyone with SSH access can all share a Ledge notebook. But that probably doesn't get us all the way there.
Thanks again for providing your thoughts. This by no means is a solved problem but I'm interested to see where it goes!
- env vars parametrization: this is an issue I've hit myself and am looking to add a solution for it. Created an issue for it: https://github.com/ledgesh/ledge/issues/9
- CLI: Ledge does have a CLI. One gap is it can't run a code block from the CLI - another good item to add. Created as an issue: https://github.com/ledgesh/ledge/issues/10
- flags: you can add flags in the codeblock in Ledge (like confirm, norun, etc)
Thanks for the great input!