Comments (10)
Given that Container names may be long, and Services may have multiple containers associated with them, I'm increasingly inclined towards a UI like this:
I would be curious to hear what other people think of this, and how other people would expect it to work. If there's enough interest in this approach, I may go ahead and try to move it forward myself...
from lazydocker.
Nice to hear :)
My thoughts is, make it default:
gui:
showContainerName: true
And if someone dont want the container name then they can set it to false
.
If if there is no more space in horizontal then you can show like these examples:
running thisIsNameOfService (..) 0.00%
(service name is long then add (..) to container name
same on the other way.
And when you click on this service it will show a header on the left windows where Logs, Stats, Container Config, Top
is and show the container name on the header.
from lazydocker.
Happy to have a look into this over christmas break if that's ok
from lazydocker.
Hi, is anyone working on it, otherwise I would like to pick this up
from lazydocker.
Sounds like a reasonable request. Given that there if often not much horizontal space, I'm inclined to make this a user configurable thing that defaults to false. Something like:
gui:
showContainerName: true
What are your thoughts on that approach?
As for implementation, It would be fairly trivial to write the code, it would just be a matter of changing the GetDisplayStrings() function in pkg/commands/service.go
. I'm happy to label this as Good First Issue and see if anybody wants to pick it up (I'm happy to lend a hand) :)
from lazydocker.
My $0.02: I don't really want or need to see the container name in the sidebar (in the header of the main panel would be great though!) unless the service has a dynamic container_name. Knowing what directory lazydocker is running in would be more useful.
My primary use case is in development, where I run a few distinct projects that share service names. My services have static container names to make linking them together easier, and I'm never running a service as more than a single instance. If/when I cannot supply a container name (e.g. swarms), I'd still like to see the service listed, along with the specific containers.
from lazydocker.
@pvande how about instead of having lazydocker
in the status panel in the top left, we have the name of the current directory?
As for dynamic container names, I wonder how easy it is to see if a container name is dynamic.
@mudasar187 I'm hesitant to use the ellipsis approach because it seems to me that people either want to know what the container name is or not, and if they have no way to expand the width of the side panels, they can't really access that information. This makes me think we should probably support having a short and long sidepanel view for when you want everything you need in tabular form, but that's a separate issue.
If we could find a way to check if a container name was dynamic, and if so, show it in brackets, would that satisfy both your use cases?
from lazydocker.
@jesseduffield Yeah, i think thats a better suggestion :)
from lazydocker.
@jesseduffield I would have suggested putting it in that status panel, but I didn't want to suggest losing the branding!
As for dynamic container names, I'm more or less working from the definition "the docker-compose service does not specify a container_name
key". That may not be perfectly adequate, but it seems like a good starting point.
from lazydocker.
Please, go ahead.
from lazydocker.
Related Issues (20)
- Installation fails on Fedora 38 with GO 1.20.8
- Unknown memory leak
- Update version execution error: could not determine host context "default" does not exist HOT 12
- Docker image missing 1.20-3.15 HOT 4
- Changed DOCKERFILE with existing hub image
- After running lazydocker, docker completely breaks and it starts to require root permissions HOT 2
- Cannot install on Debian 5.10.197-1 via curl .sh HOT 2
- Custom Colors/Theme Config
- Possibility to configure different servers to manage the Dockers and have then split on "tabs" HOT 4
- Request: View only mode
- Enhance Image Section with Active Use Indicator HOT 2
- Connecting to remote docker host over ssh is broken
- XDG base directory specification is not described in the config docs
- Config options for side panel visibility / size HOT 1
- Rounded Corners
- can't install following README instructions HOT 1
- Installing on arch linux using yay fails HOT 3
- Can I pass a flag to set the Project Name to something ?
- Cannot proceed until docker gives us more information about the container. Please retry in a few moments.
- Move the panel with number like lazygit
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lazydocker.