The env variable is within the compose file itself - it's fairly simple.
lka1988
joined 5 months ago
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.
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.
My work laptop has W11. It's....fine. But I don't have to manage it, so... ¯\(°_o)/¯
I had W11 on my personal gaming PC for a total of 6 months before I got fed up with it. Running W10 until I make sure it'll run everything I need it to on Linux Mint (LMDE).
I mean, yes, but...what the fuck 😂
That's what W10 LTSC is for.
It's used for industrial applications like manufacturing and whatnot, stuff that really doesn't need to be updated regularly since the software is effectively legacy.
Hell, we've got tools from the 2000s still running Win2k.
I've had the oil in my 2008 Sienna analyzed a few times by Blackstone Labs, and have been told that 5k miles is what I should stick to.
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.