It is an attempt at recreating the lazydocker command-line application from scratch, while making it available as a web application without compromising on the features.
Wouldn't it be possible to directly use lazydocker with a browser terminal such as wetty?
I would think so! Looks like the author tried some similar approaches.
In the disclaimer section:
> Before creating Isaiah, I tried to "serve lazydocker over websocket" (trying to send keypresses to the lazydocker process, and retrieving the output via Websocket), but didn't succeed, hence the full rewrite.
> I also tried to start Isaiah from the lazydocker codebase and implement a web interface on top of it, but it seemed impractical or simply beyond my skills, hence the full rewrite.
I took a crack at something like this a couple of weeks ago[0] except using ttyd. It’s been working pretty well since then and I actually really enjoy the setup.
This reminds me of k9s, particularly the UI and full functionality. I use dockge https://github.com/louislam/dockge for managing stacks on a home server. Isaiah feels very admin oriented, or perhaps developer friendly for that full docker experience via the web.
I only had a brief play but I couldn't see how to deploy a new container. That would make this a companion tool alongside something like Dockge, portainer etc.
- From an image (in the "Images" tab), you can open the menu, and run the image as is (or press "r"). You will be prompted for a container's name, and it will be created.
- You can press "C" (for Create stack), fill in a docker-compose.yml file content, and confirm. This will create a stack from your file!
Curious why people feel the need for tools like this. I think git benefits massively from a graphical tool but I don't really see the point for docker, docker compose or even kubernetes. I do find CLI completions essential, though.
Docker benefits from a graphical tool for the same reason as git does; both CLI tools often require using long id strings from the output of one command as the input of another command.
CLI is good and the best way to manage docker containers, however editing that compose file from a browser tab and hitting recreate slaps different. A web GUI makes it so that users who are otherwise intimidated by CLI can still make use of docker.
I would be worried about where that compose file is being stored. I keep my compose files in a git repo and after I edit them just do `docker compose up -d` (in fact, I hit a key in my editor and it runs that for me, showing the output).
Portainer is mentioned by the author in the README:
“What spurred me to build Isaiah in the first place is a bunch of comments on the Reddit self-hosted community, stating that Portainer and other available solutions were too heavy or hard to use.”
I like the idea of a web based text ui. But if it's a clone of an existing cli tool this seems to be going full circle, just use ssh or a web ssh client. Still a nice project though :)
Alright! I'll copy-paste an explanation I gave prior on Reddit. I legit had no idea this would spark so many conversations hahaha.
"I like to use a pen name generator, and use the generated name for my projects. It makes it easier for me to name things, rather than having to come up with new naming ideas for every new project. And also, I like the idea that every project has a person's name, as if, by using the project, you're getting the help of the person named X (X = Isaiah, Erin, Osmond, any other project I have published)."
I really had never thought of the religious aspect of Isaiah, I just went with a generated pen name I liked.
To me names are important. I have to find a good name for a project or business before I start. Or at least good-enough. This is a great naming idea. I love it.
Readit News
In the disclaimer section:
> Before creating Isaiah, I tried to "serve lazydocker over websocket" (trying to send keypresses to the lazydocker process, and retrieving the output via Websocket), but didn't succeed, hence the full rewrite.
> I also tried to start Isaiah from the lazydocker codebase and implement a web interface on top of it, but it seemed impractical or simply beyond my skills, hence the full rewrite.
[0] https://github.com/mattpowell/lazydocker-web
I only had a brief play but I couldn't see how to deploy a new container. That would make this a companion tool alongside something like Dockge, portainer etc.
To deploy a new container, you have two options :
- From an image (in the "Images" tab), you can open the menu, and run the image as is (or press "r"). You will be prompted for a container's name, and it will be created.
- You can press "C" (for Create stack), fill in a docker-compose.yml file content, and confirm. This will create a stack from your file!
Let me know if I can help!
“What spurred me to build Isaiah in the first place is a bunch of comments on the Reddit self-hosted community, stating that Portainer and other available solutions were too heavy or hard to use.”
Deleted Comment
Deleted Comment
Deleted Comment
Deleted Comment
"I like to use a pen name generator, and use the generated name for my projects. It makes it easier for me to name things, rather than having to come up with new naming ideas for every new project. And also, I like the idea that every project has a person's name, as if, by using the project, you're getting the help of the person named X (X = Isaiah, Erin, Osmond, any other project I have published)."
I really had never thought of the religious aspect of Isaiah, I just went with a generated pen name I liked.
Dead Comment
You are thinking of Noah and the Whale.
https://en.m.wikipedia.org/wiki/Noah_and_the_Whale
You are more likely thinking of Jonah and the Whale.
https://en.wikipedia.org/wiki/Jonah
Deleted Comment