Update README.md

pull/10/head
Jesse Duffield 5 years ago committed by GitHub
parent 2be1658ff0
commit 577a778cda
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -8,16 +8,11 @@ A simple terminal UI for docker, written in Go with the [gocui](https://github.c
![Gif](/docs/resources/demo.gif)
Are YOU tired of this workflow:
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`. 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.
- recognise your local server isn't responding
- run `docker ps`
- see your container exited
- place mouse at beginning of the container ID, drag to the end of the container ID
- press cmd+c
- run 'docker restart <cmd+v>'
What a headache!
sounds like you might want to give lazydocker a try!
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. Lazydocker's goal is to make that dream a reality.
![Gif](/docs/resources/lazydocker-example.gif)
@ -68,7 +63,8 @@ everything is one keypress away:
- viewing the state of your docker or docker-compose container environment at a glance
- viewing logs for a container/service
- viewing cool ascii graphs of any container with any metric you want to measure (e.g. CPU percentage, memory usage)
- viewing ascii graphs of your containers' metrics so that you can not only feel but also look like a developer
- customising those graphs to measure nearly any metric you want
- attaching to a container/service
- restarting/removing/rebuilding containers/services
- viewing the ancestor layers of a given image
@ -76,7 +72,7 @@ everything is one keypress away:
## Contributing
We love your input! Please check out the [contributing guide](CONTRIBUTING.md).
There is still a lot of work to go! Please check out the [contributing guide](CONTRIBUTING.md).
For contributor discussion about things not better discussed here in the repo, join the slack channel
[![Slack](/docs/resources/slack_rgb.png)](https://join.slack.com/t/lazydocker/shared_invite/enQtNDE3MjIwNTYyMDA0LTM3Yjk3NzdiYzhhNTA1YjM4Y2M4MWNmNDBkOTI0YTE4YjQ1ZmI2YWRhZTgwNjg2YzhhYjg3NDBlMmQyMTI5N2M)

Loading…
Cancel
Save