Default config is defined in the firmware. It can’t be deleted or changed (well, easily. I think there is a reseller option to have a custom default config).
The “no default config” means the default config will not be applied after the reset.
If you reset it again without checking “no default config”, then the default config will be applied.

“No default config” is very useful for applying your own config script. It gives you a blank canvas, making scripting a lot easier!

I have my “config.rsc” file that has the required configuration. And I have a “reset.auto.rsc” file that only has the command to reset the mikrotik with no defaults and to run the “config.rsc” script after reset.
“filename.auto.rsc” will be executed as soon as it gets FTPd (it’s a feature of mikrotik).
I use a bash script that FTPs the config.rsc file to the mikrotik, then the reset.auto.rsc file.
Makes it trivial to tweak the config then apply it, and I get all the config for the devices in easy to edit/diff script files.

It’s the number of families that think their kid/husband/father is missing

The best thing is: if something doesn’t work, you tweak the compose file instead of having to retype or edit a command.

And you can have a GitHub of your compose files and any supporting config files.

I don’t get how some people can raw dog a docker run command!

America can’t do 2 things at once?
I mean, they aren’t even doing 2 things. They’re saying “yeh go for it”, and then America can turn it’s full attention on itself.

Back when Blockchain was first a huge hype bubble, there were companies that added “Blockchain” to their name, or announced a pivot into Blockchain tech, and watched their stock value soar by a few hundred percent (with market value being many times their revenue).
I had googled a list of news articles, until I found this:
https://www.sciencedirect.com/science/article/abs/pii/S0165176519301703

A noteworthy example: https://www.cnbc.com/2017/12/21/long-island-iced-tea-micro-cap-adds-blockchain-to-name-and-stock-soars.html

Anyway.
That’s the bubble.
Over-valuation. People taking advantage of the hype. People jumping on any opportunity to “not be left out” or to “get in early”.

AI has uses.
Everyone is throwing things at the wall to seeing what sticks. Not much of it will.
Marketing are capitalising on the hype.

As a hobby developer, I feel like I’m just gluing libraries together to get what I want.

Server hardware does.
I think dell Rx30 are only just getting to EOL, and it was released in 2015.

Although, buying an Rx30 before 5 years ago would be in the 10s of thousands.
Refurbished Rx40 and Rx50 are somewhat affordable.

If you want remote access to your home services behind a cgnat, the best way is with a VPS. This gives you a static public IP that your services connect to, and that you can connect to when out and about.

If you don’t want the traffic decrypted on the VPS, then tunnel the VPN back to your homelab.
As the VPN already is encrypted, there is no point in re-encrypting it between the vps and homelab.

Rathole https://github.com/rapiz1/rathole is one of the easiest I have found for this.
Or you can do things with ssh tunnels.

For VPN, wireguard is very good

You can set a static IP on the router, disable it’s DHCP, and have pihole manage DHCP with the routers static IP as the gateway

I can say I’ve never glorified suicide. When I’ve been suicidal, suicide is literally the only logical solution my brain can arrive at. It’s completely irrational in hindsight, but it makes so much sense at the time.

I don’t think I have ever not-watched something due to content warnings alone. But it has alerted me that there may be issues, so it doesn’t surprise me when it comes up.

A technical reason is because he has been a president before

I would say the more regular expiration and renewal of an LE cert is better.
It’s an ongoing check instead of an annual check.

At the homelab scale, proxmox is great.
Create a VM, install docker and use docker compose for various services.
Create additional VMs when you feel the need. You might never feel the need, and that’s fine. Or you might want a VM per service for isolation purposes.
Have proxmox take regular snapshots of the VMs.
Every now and then, copy those backups onto an external USB harddrive.
Take snapshots before, during and after tinkering so you have checkpoints to restore to. Copy the latest snapshot onto an external USB drive once you are happy with the tinkering.

Create a private git repository (on GitHub or whatever), and use it to store your docker-compose files, related config files, and little readmes describing how to get that compose file to work.

Proxmox solves a lot of headaches. Docker solves a lot of headaches. Both are widely used, so plenty of examples and documentation about them.

That’s all you really need to do.
At some point, you will run into an issue or limitation. Then you have to solve for that problem, update your VMs, compose files, config files, readmes and git repo.
Until you hit those limitations, what’s the point in over engineering it? It’s just going to over complicate things. I’m guilty of this.

Automating any of the above will become apparent when tinkering stops being fun.

The best thing to do to learn all these services is to comb the documentation, read GitHub issues, browse the source a bit.

Bitwarden is cheap enough, and I trust them as a company enough that I have no interest in self hosting vaultwarden.

However, all these hoops you have had to jump through are excellent learning experiences that are a benefit to apply to more of your self hosted setup.

Reverse proxies are the backbone of hosting and services these days.
Learning how to inspect docker containers, source code, config files and documentation to find where critical files are stored is extremely useful.
Learning how to set up more useful/granular backups beyond a basic VM snapshot in proxmox can be applied to any install anywhere.

The most annoying thing about a lot of these is that tutorials are “minimal viable setup” sorta things.
Like “now you have it setup, make sure you tune it for production” and it just ends.
And finding other tutorials that talk about the next step, to get things production ready, often reference out dated versions, or have different core setups so doesn’t quite apply.

I understand your frustrations.

In France, no one spoke English even though I spoke loudly and slowly

Haha, reminds me of a holiday ages ago in France.
Someone left their handbag behind or something, and my friend said “I’ll sort it out, I know French”. To be fair, he did. But when I went back to tell him where we ended up, he was speaking slowly and loudly to the poor french person.

Which reminds me of another time in France, having breakfast. I ordered “orange juice” and the waiter looked confused. So I said it again slower, and his face lit up and said “ah, jus d’orange”.

Yeh, seems not

I felt like adding something about the specific case of 180° between edges and a vertice.
Makes sense.
And I guess too many vertices means an open set of edges (ie not close, this not a shape).
I was kinda hoping for a strange edge case, like a mobius strip or Klein bottle.

I guess a mobius strip is a 2d representation of a 1d paradigm. And a klein bottle is a 3d representation of a 2d paradigm.
It would be too much to ask of a 1d representation of a ??d paradigm.

I feel my comment adds to the discussion and wants more details.
But it was too simply phrased.
I guess the details of such a question should be obvious. And if you need the details, the question doesn’t actually add the the discussion… It just seems idiotic!

I felt like there might be a really cool scenario where a vertice isn’t considered a vertice.
Like, there actually might be some case on a 2d plane “where actually” applies.
I’m fine being wrong

What if it had 3 corners and 4 edges? Or 4 corners and 3 edges?

Just wait until you learn about the etymology of triceratops