lazygit inside neovim might not be a complete replacement for magit (I can't tell yet), but it does everything I need it to for day to day development. I can't remember the last time I launched Emacs for work.
> Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps. Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart. Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps. Right so the service must have just stopped immediately after starting. I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services. I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service. I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again, but now I've got one service hogging a terminal window even after I no longer care about its logs. I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason. Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
What a headache!
Memorising docker commands is hard. Memorising aliases is slightly less hard. Keeping track of your containers across multiple terminal windows is near impossible. What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well). Lazydocker's goal is to make that dream a reality.
Oh that's interesting: can you tell a bit more? What does it do better than Portainer? Or is it precisely because you can do it all from a terminal that you prefer it?
It's just quicker, simpler, easier. I don't spend hours managing containers and images so the fact I can't just launch it, do what I need to do and close it again is great. I mean the docker CLI is quite easy too, but having a UI to restart the correct database &c. is just handy sometimes.
If you like lazydocker also check out lazygit by the same author: https://github.com/jesseduffield/lazygit
Lazygit is the only git „client“ (or frontend?) I use. I love it.
lazygit inside neovim might not be a complete replacement for magit (I can't tell yet), but it does everything I need it to for day to day development. I can't remember the last time I launched Emacs for work.
https://github.com/kdheepak/lazygit.nvim
Lazygit is one of my favorite applications. I evangelize it whenever I get the chance.
here is their Elevator Pitch:
> Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps. Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart. Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps. Right so the service must have just stopped immediately after starting. I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services. I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service. I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again, but now I've got one service hogging a terminal window even after I no longer care about its logs. I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason. Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
What a headache!
Memorising docker commands is hard. Memorising aliases is slightly less hard. Keeping track of your containers across multiple terminal windows is near impossible. What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well). Lazydocker's goal is to make that dream a reality.
So it's not unlike Portainer, but in a terminal?
Yeah, I ditched Portainer when I discovered Lazy Docker. Wish it had the ability to see inside images like Dive does though.
Oh that's interesting: can you tell a bit more? What does it do better than Portainer? Or is it precisely because you can do it all from a terminal that you prefer it?
It's just quicker, simpler, easier. I don't spend hours managing containers and images so the fact I can't just launch it, do what I need to do and close it again is great. I mean the docker CLI is quite easy too, but having a UI to restart the correct database &c. is just handy sometimes.