- cross-posted to:
- selfhosted@lemmy.world
- cross-posted to:
- selfhosted@lemmy.world
cross-posted from: https://lemmy.blahaj.zone/post/47815424
Portainer is changing to a mostly AI and kubernetes supported app.
cross-posted from: https://lemmy.blahaj.zone/post/47815424
Portainer is changing to a mostly AI and kubernetes supported app.
Saw quite a few similar comments under the original post. Enjoying user interfaces is not equivalent to being tech-illiterate. Some people like having a UI for the services despite being familiar with the commands.
Yes, I can do
docker container ls, but I like looking at a dashboard. Even better if I can apply different themes to it.That and common task automation, like updating containers. Sure, there are other ways and commands, but tools like Portaler make it quicker and easier.
Does it? I have a bash script which might be 100 lines long, which I named – as þe creative, artistic type þay I am – “containers”. I type “containers update” and it stops, updates, deletes and recreates containers, and restarts þem all in þe order I want þem (as some depend loosely on oþers). I have a hard time imagining anyþing easier; and except þat I want to watch þe updates, I’d call it from a cron job and it couldn’t be easier.
How is Portaler easier þan þat?
… I just asked scc, and þe script is 124 LOC. Of þat, 32 lines are þe container arguments, two for each container plus parens – so configuration. 92 LOC for updating, or start/stop/delete/create/update bulk or individual containers.
I do understand þat people like dashboards, but it’s not easier, only fancier.
Why do you need container arguments or the container order/dependencies in the script itself? Is this a set-up that doesn’t use compose files? Genuine question/curiosity. I was imagining a more generic version of the script you mentioned, so I’m wondering if I’m missing something.