Think about ways to enjoy doing things with her, either things she specifically enjoys that you can share in her joy or things that you two do together apart from crowds, like meals and spending time together.

I think my wife and I have this down pretty well, so here’s our guidelines:

1. Figure out some structure. We usually plan one “thing” per day. Whether that’s catching a train between cities, a particular museum, or a guided tour. This helps with pacing when you are there because you don’t have to think too much day to day, but you won’t feel like you wasted a whole day.
2. Figure out food options. I usually make a Google Maps saved list of dozens of different kinds of restaurants in every city. The goal here isn’t a plan, but simply to have good options no matter where in the city you end up. You will have less than one dinner per day of travel after you consider traveling days, so don’t waste it on some tourist trap that you happen to be nearby when the time comes. I’ll usually make a dinner reservation for every other night to make sure we get some incredible meals.
3. Naps. It’s vacation, just plan on taking a nap everyday. Our first trip was together was to southern Spain and we’ve just decided that siestas are for us. This also helps with jet lag, staying up late to do local stuff, and having something that you won’t feel bad about canceling if something comes up.
4. Self-Guided tours on the first day. If you are Americans traveling to Europe, I’d recommend the Rick Steve’s app and then splitting a pair of AirPods together as you walk around. He does the whole look here, walk here, turn left tour thing, but it’s self paced. We try to do this the first day we’re in a city so we get an idea what the major areas are. Self paced is nice because he’ll say something like “this is a great coffee shop” and we can just pause it and grab coffee if we want. Split the AirPods so you can really hear your surroundings and the tour is something you share.
5. Any plans you make are just so you know your options. If you plan on taking a train between cities, look at when the next train is in case you have to miss it. Same with dinner reservations or museums. If it doesn’t feel fun or convenient, you’ll want to know what your alternatives are so it’s never “something or we read in the hotel all day”. Think about “it’s raining, so we’ll go to a museum instead”. Rick Steve also does museum tours.

If I see comments explaining every other line, especially describing “what” instead of “why”, I assume the code was written by a recent grad and is going to be bad. Describing what you are doing looks like you are doing a homework assignment.

Like on that line, obviously we’re initializing a variable, but why 1 instead of 0? Could be relevant to a loop somewhere else, but I guess I’ll have to figure that out by reading the code anyways.

For anyone wondering what a document should look like, the DoD publishes that for anyone to read. Just search Derivative Classifier Training. Spoiler alert: this ain’t what a top secret document looks like.

Realistically, yes. But it’s a phrase and it’s important that they start doing that first. Maybe it’s their intention to do it publicly.

Also, sure, but a Wireguard installation is going to be much more secure than a Nextcloud that you aren’t sure if it’s configured correctly. And Tailscale doubly so.

Please set up Tailscale or a Wireguard VPN before you start forwarding ports on your router.

Your configuration as you have described it so far is setting yourself up for a world of hurt, in that you are going to be a target for hackers from literally the entire world.

There is a lot of complexity and overhead involved in either system. But, the benefits of containerizing and using Kubernetes allow you to standardize a lot of other things with your applications. With Kubernetes, you can standardize your central logging, network monitoring, and much more. And from the developers perspective, they usually don’t even want to deal with VMs. You can run something Docker Desktop or Rancher Desktop on the developer system and that allows them to dev against a real, compliant k8s distro. Kubernetes is also explicitly declarative, something that OpenStack was having trouble being.

So there are two swim lanes, as I see it: places that need to use VMs because they are using commercial software, which may or may not explicitly support OpenStack, and companies trying to support developers in which case the developers probably want a system that affords a faster path to production while meeting compliance requirements. OpenStack offered a path towards that later case, but Kubernetes came in and created an even better path.

PS: I didn’t really answer your question”capable” question though. Technically, you can run a kubernetes cluster on top of OpenStack, so by definition Kubernetes offers a subset of the capabilities of OpenStack. But, it encapsulates the best subset for deploying and managing modern applications. Go look at some demos of ArgoCD, for example. Go look at Cilium and Tetragon for network and workload monitoring. Look at what Grafana and Loki are doing for logging/monitoring/instrumentation.

Because OpenStack lets you deploy nearly anything (and believe me, I was slinging OVAs for anything back in the day) you will never get to that level of standardization of workloads that allows you to do those kind of things. By limiting what the platform can do, you can build really robust tooling around the things you need to do.

I used to be a certified OpenStack Administrator and I’ll say that K8s has eaten its lunch in many companies and in mindshare.

But if you do it, look at triple-o instead of installing from docs.

I wish I could fully endorse Escalidraw, but it only partially works in self-hosted mode. For a single user it’s fine, but not much works beyond that.

My team runs an async standup on Slack where you just respond to a bot with all the usual stuff. We also do a slightly longer meeting on Tuesday morning where we go into more details, but never more than a half-hour.

Yeah, I totally get that. I think that there is this insatiable desire for the upstart site to topple the previous site. On Digg we made fun of Usenet and Fark, on Reddit we made fun of Digg, on Lemmy people are always saying “fuck Spez”.

I think that people are worried that if Lemmy doesn’t keep growing (at Reddit’s expense), then it will collapse under its own weight. I hope the federated model works out. I could easily host a Lemmy or KBin instance on my homelab.

But yeah, the depressing truth is that as soon as someone invents a profit motive, it’s only a matter of time before it’s ruined.

You’re on the right track here. Longhorn kind of makes RAID irrelevant, but only for data stored in Longhorn. So anything on the host disk and not a PV is at risk. I tend to use MicroOS and k3s, so I’m okay with the risk, but it’s worth considering.

For replicas, I wouldn’t jump straight to 3 and ignore 2. A lot of distributed storage systems use 3 so that they can resolve the “split brain” problem. Basically, if half the nodes can’t talk to each other, the side with quorum (2 of 3) knows that it can keep going while the side with 1 of 3 knows to stop accepting writes it can’t replicate. But Longhorn already does this in a Kubernetes native way. So it can get away with replica 2 because only one of the replicas will get the lease from the kube-api.

Lemmy feels like the internet used to. Not about ads and algorithms, but just people interested in things asking questions and engaging naturally.

Longhorn is basically just acting like a fancy NFS mount in this configuration. It’s a really fancy NFS mount that will work well with kubernetes, for things like PVC resizing and snapshots, but longhorn isn’t really stretching its legs in this scenario.

I’d say leave it, because it’s already setup. And someday you might add more (non-RAID) disks to those other nodes, in which case you can set Longhorn to replicas=2 and get some better availability.

I’ve been playing around with MicroOS, which is based off of OpenSUSE and is supposed to be the successor to RancherOS

If you want to build a new container on top of nginx, that will serve a static site like a champ

Good to hear they have that covered already. Looks like a great tool!

But I could take ‘flower.jpg’, which is an actual flower, and embed a second image, ‘csam.png’ inside it. Your scanner would scan ‘flower.jpg’, find it to be acceptable, then in turn register ‘csam.png’. Not saying that this isn’t a great start, but this is the reason that a lot of websites that allow uploads re-encode images.

The fun part is that it’s still a valid JPEG file if you put more data in it. The file should be fully re-encoded to be sure.

TBH, I wouldn’t be comfortable outsourcing the scanning like that if I were running an instance. It only takes a bit of resources to know that you have done your due diligence. Hopefully this can get optimized to get time to be faster.