Lka1988

I did the same shit as a teenager, big fucking whoop. How about we focus on the Nazi part of this asshole.

Same here! We had it on a Macintosh LC 575. I will never forget those sound effects haha.

The hypocrisy is that if an average person did something like this (such as, IDK, Aaron Schwartz) they would have already been swiftly prosecuted and made out to be an example of “look what will happen to you”.

It’s just the two-tiered justice system being what it is, again.

For me it depends which bike I’m riding. If it’s my 49cc scooter, I’ll sit to the very right side of the lane for a quick escape while watching my mirrors like a hawk. On my XR500, I’ll just filter to the front (legal in Utah).

Good to know, I’ll stay away from those damn things when I ride.

“CRUD”, “Sham” coin, and yesterday’s date…

🤨

It’s the hypocrisy, not the law

Ah haha, the IT/IS department at the last company I worked for saw right through that and nailed me to the wall for “unauthorized VPN usage” 😂😂

(a mid 2010’s macbook running debian)

Brave soul. My wife has a 2017 A1706 MBP… We also have a 2009-ish MBP loaded with Linux Mint that the kids use for schoolwork.

The only reason I’m posting from my shit account right now (I still like this place, don’t worry) is because db0 is blocked at work for “PiRaCy” 🙄🙄🙄

Nevermind, I guess IT decided to unblock it.

I haven’t experienced this, oddly enough. Many of my compose files have comments, and they’re still visible 🤔

Let us know if you run into more snags! I’m happy to try to help out. I also revised my comment above several times last night and this morning as I was really tired and kept forgetting details 😅

The other thing to note is the “Scan Stacks Folder” option in the drop-down menu. I haven’t really needed to use it as Dockge tends to find my compose files on its own, but it’s worth mentioning.

It’s needed because that’s how Dockge manages the compose files - it needs to know where your compose files live. Dockge normally lives in it’s own directory, /opt/dockge/ (the dev gave a reason for that, but I don’t remember why), so it won’t see anything else until you point it to wherever your compose files are normally located.

The env variable is within the compose file itself - it’s fairly simple.

Oh I love this stuff.

My dishwasher pulls over 1000W, but overall actual usage pales in comparison to my server cluster, which utilizes a multiple 35W mini PCs.

I started measuring a bunch of things in February (using zigbee-compatible smart plugs to HA), so here is a graph of the above for the entire month of March:

It was eye opening, to say the least.

People complaining about this video have clearly not watched much Technology Connections; I enjoyed it immensely. It’s right in line with how Alec normally does his videos. We who are loyal to the Great Alec expect the pedantic content.

I swear to fuck, you guys take a single thing and just run the absolute shit out of it.

Proton is run by the Proton Foundation. Andy Yen is only one of FIVE members of that board (including the literal father of the internet, Tim Berners-Lee, who is a well-known proponent of internet privacy and who’s voice likely holds a lot more weight than Andy). Andy fucked up by using the official Proton account to post a personal opinion about ONE person that was NOT trump. He overexplained it later on trying (and failing horribly) to do damage control, after which the rest of the board likely told him to just shut the fuck up.

THAT’S ALL THAT HAPPENED. Proton itself is a perfectly fine service.

I think you might be misunderstanding here, Dockge doesn’t really work like that. You don’t import “into” Dockge - it works alongside Docker, and all you need to do is point it to where your compose files are located. Which, like I said, is normally set to /opt/stacks/ - but that’s not set in stone and can be changed to another location via the DOCKGE_STACKS_DIR= env variable within Dockge’s own compose file (located in /opt/dockge/).

For example: Say I create the directory /opt/stacks/docker_container/, drop in my “docker_container” compose.yml file, and fire it up in the terminal with docker compose up -d, all via CLI without touching Dockge at all. Dockge will still automatically see the compose file and the stack status. Or, say I have a previously-established Docker host with all the compose files in a location such as /home/username/docker_stacks/, and I really don’t want to move them - so long as Dockge is configured to point at that directory, and the directory contains a labeled folder for each compose file (just like you would do normally), again, Dockge will automatically see the compose files and stack status. I’ve configured multiple hosts to use Dockge, and it’s really that simple.

Also, something I just remembered - the directory structure for your compose files, wherever it’s located, needs to be all lowercase. Otherwise Dockge won’t see it.

You’re not wrong; I was just being hyperbolic.

If the compose.yml can be moved to a place where Dockge is configured to look, then yes. Normally it’s configured to look in /opt/stacks/, but that can be changed.

An immutable distro would be ideal for this kind of thing. ChromeOS (an immutable distro example) can be centrally managed, but the caveat with ChromeOS in particular is that it’s management can only go through Google via their enterprise Google Workspace suite.

But as a concept, this shows that it’s doable.