The constant argument in this space that you must know the arcane workings of everything you use, is exhausting.
Mastodon: @SeeJayEmm@noc.social
The constant argument in this space that you must know the arcane workings of everything you use, is exhausting.
Just because something doesn’t fit your use case doesn’t make it a terrible product. Portainer isn’t meant to complement managing docker via CLI. It’s meant to be the management interface.
If you want to manage your environment via CLI, I agree, don’t use Portainer. If you’re content (or prefer) a GUI, Portainer is a solid option. Esp if you have multiple hosts or want to manage more than just the compose stack. Last time I checked Dockge doesn’t do either.
Personal preference? I prefer the Portainer’s presentation over the CLI. I especially find it easier to manage networks and volumes.
But my main reason is I have multiple docker hosts and it gives me a “single pane on glass” to manage everything from.
Heaven forbid I want to use an intuitive, simple, terminal based text editor when I ssh into one of my boxes.
But here’s the real kicker. Why do people like you give two shits what text editor other people use?
Appears to work as well as it does on windows. I guess the only downside is learning powershell if you have no previous experience with it.
I forgot where I was posting. (I use both win and Linux pretty heavily.) I have pwsh, let me see if import-excel works on linux and report back.
For Excel there is a PowerShell module called Import-Excel that I use all the time.
Yes to all of that.
Turns out it was a content update that caused the driver to crash but the update itself wasn’t a driver (as per their latest update.)
Is feel a lot better about this if it was a “supporter” tag not this “unlicensed” crap.
I was really hoping this was going to be a rant about clouds in the sky.
That’s the business ed not the community. There’s no limit in aware of in the community ed
Wiki.js Nginx Proxy Manager.
Enough people have already commented on the “proxy at the vps solution”. Another option is to configure routing and nat on the VPS and have it route over the wg tunnel.
Requires you to have postup/predown scripts that modify your routing tables on the wg endpoint.
I made the plunge about a year ago. Spectrum assigns me a prefix but routing was spotty at best. In the end after all the troubleshooting pointed to the problem being the ISP I gave up and stuck with what works, IPv4.
https://www.wireguard.com/protocol/
Looks like wireguard encrypts traffic to me.
Even with an outlet who wants to slow charge a plug-in EV? The infrastructure isn’t there and the cars are too expensive.
Only by exposing the docker socket. And it doesn’t support managing network or volumes.