Yeah, nothing special about the markings. Whatever looks best.
Kovukono
Sadly, the only decent pic is what's on the easel from this vent art. In case it's not recognizable, it's a snow leopard. And yours?
A headshot of someone's sona, absolutely. But if you'd prefer a trade, we might be able to do that. You just have to bear with the fact that I've got next to no art of my sona.
The only guy I considered was Elliot, but between the girls it was Leah, Abigail, Haley, or maybe Maru. I wound up with Leah, but it felt like the girls in general were a lot more interesting than the guys.
I get that, but you're also not quite getting the full picture with this specific instance. The community on Reddit has been waiting for Silksong so long that they have been over-analyzing every single game convention for years to see if we're going to get a release date, and had a heated debate over whether or not a blood sacrifice of a member of the community would bring the release. They're a little crazy over there.
I got super-excited when I saw they were bringing back Peter Stormare--and then worried when this looked nothing like the game.
I love how it basically swings between entirely accurate and wildly inaccurate, and there's no clean line for it.
You have a computer. That computer does exactly one thing, and anyone can make a copy of it, and tweak it slightly to fit their needs. That's a Docker container. It needs to run on other computers.
You need a way to manage multiple Docker containers, and the networking between them, and the items you need to customize them. You also want to make sure that they aren't going to bump into each other accidentally, so you need to sequester them in different areas. You also need to make sure that only certain people have access to those different areas, so you set up authentication in a fashion that reflects that. You also need to manage the computers the Docker containers are running on, to make sure that only certain hosts run certain workloads, and that there's a difference between controller and worker nodes, and that the networking is set up correctly between them, using a custom thing called a container network interface, of which there're multiple choices and you need to decide which best fits you needs. You also need to make sure that you have a permanent storage solution that the Docker containers can use, so that if you lose a worker node you don't lose all the data for all the containers running on it. All of this is run through API calls to the controller nodes. That's what I remember off the top of my head for Kubernetes, and I think I'm forgetting stuff.
We aren't crying because of you, we did this to ourselves.
Thank you! Unfortunately, I've now definitely given them photo evidence of the warranty being violated, lol.
I'm not sure how much more detail you could have added, it looks great is it is. It sucks that the relationship turned out badly, but I'm hoping this next year works out better for you.
Sure thing! What's your sona?