Borderlands. How did they spend that much money and none of the decision makers stop and think "nope this is crap"
scrubbles
joined 2 years ago
MODERATOR OF
Interesting, my DVDs and blurays appear to still be right there on the shelf.
First intro to MtG was in college I walked past a room with the lights out and only candles lit, the four people were wearing robes and playing... MtG. Decided right then that nah, that's too far for me.
Seriously what is the deal with it? I remembered playing it in gym decades ago and everyone hated it. Now I see people lobbying for new freaking complexes for it. Let's see if the fad lasts more than a year before dedicating public land space to it
We've been eclipsed in so many other ways - and now we will here too. We'll still eventually get to full green, that just makes that process slower, but in the meantime we're just letting others pass us by.
I wonder what they'll do with all that money they aren't spending on fossil fuels.
Glad to be of help. It is the right decision, I have no regrets if migrating, but it is a long process. Just getting my first few services running was months, just so you are aware of that commitment, but it's worth it.
Agreed on all points, and also would like to point out most of the people who want to "go back" are not the ones who were oppressed during that time. It's no surprise that the people who want to go back are mostly those who grew up in the white suburbs and small towns, where it was simple and easy.
The oppressed are conveniently left out of those conversations. Where were the black people, or the gay people during those times? They existed, but in a very simple worldview it's easy to forget that.
Yeah, unfortunately most people don't understand what that is, and buy devices thinking they'll be supported long term. Us here know better (I bought Wemo early on and stopped years and years ago now because I knew this was coming, but I know I'm not the majority).
I'll post more later (reply here to remind me), but I have your exact setup. It's a great way to learn k8s and yes, it's going to be an uphill battle for learning - but the payoff is worth it. Both for your professional career and your homelab. It's the big leagues.
For your questions, no to all of them. Once you learn some of it the rest kinda falls together.
I'm going into a meeting, but I'll post here with how I do it later. In the mean time, pick one and only one container you want to get started with. Stateless is easier to start with compared to something that needs volumes. Piece by piece brick by brick you will add more to your knowledge and understanding. Don't try to take it all on day one. First just get a container running. Then access via a port and http. Then proxy. Then certs. Piece by piece, brick by brick. Take small victories, if you try to say "tomorrow everything will be on k8s" you're setting yourself up for anger and frustration.
@sunoc@sh.itjust.works Edit: To help out I would do these things in these steps, note that steps are not equal in length, and they are not complete - but rather to help you get started without burning out on your journey. I recommend just taking each one, and when you get it working rather than jumping to the next one, instead taking a break, having a drink, and celebrating that you got it up and running.
-
Start documenting everything you do. The great thing about kubernetes is that you can restart from scratch if you have written everything down. I would start a new git repository with a README that contains every command you ran, what it did, and why you did it. Assume that you will be tearing down your cluster and rebuilding it - in fact I would even recommend that. Treat this first cluster as your testing grounds, and then you won't feel crappy spinning up temporary resources. Then, you can rebuild it and know that you did a great job - and you'll feel confident in rebuilding in case of hardware failure.
-
Get the sample nginx pod up and running with a service and deployment. Simply so you can
curlthe IP of your main node and port, and see the response. This I assume you have played with already. -
Point DNS to your main node, get the nginx pod with
http://your.dns.tld:PORT. This should be the same as anything you've done with docker before. -
Convert the yaml to a helm chart as other have said, but don't worry about "templating" yet, get comfortable with
helm install,helm upgrade -i, andhelm uninstall. Understand what each one does and how they operate. Then go back and template, upgrade-ing after each change to understand how it works. It's pretty standard to template the image and tag for example so it's easy to upgrade them. There's a million examples online, but don't go overboard, just do the basics. My (template values.yaml) usually looks like:
<<servicename>>
name: <<servicename>>
image:
repository: path/to/image
tag: v1.1.1
network:
port: 8888
Just keep it simple for now.
- Decide on your proxy service. Traefik as you see comes out of the box. I personally use
istio. I can go into more details why later, but I like that I can create a "VirtualService" for "$appname.my.custom.tld` and it will point to it. - Implement your proxy service, and get the (http only still) app set up. Set up something like
nginx.your.tldand be able to curlhttp://nginx.your.tldand see that it routes properly to your sample nginx service. Congrats, this is a huge one. - Add the CertManager chart. This will set it up so you can create
Certificatetypes in k8s. You'll need to use the proxy in the previous step to route the /.well-known endpoints on the http port from the open web to cert-manager, for Istio this was another virtual service on the gateway - I assume Traefic would have something similar to "route all traffic on port 80 that starts with /.well-known to this service". Then, in your nginx helm chart, add in a Certificate type for your nginx endpoint,nginx.your.tld, and wait for it to be successfully granted. With Istio, this is all I need now to finally curlhttps://nginx.your.tld!
At this point you have routing, ports, and https set up. Have 2 drinks after this one. You can officially deploy any stateless service at this point.
Now, the big one, stateful. Longhorn is a bear, there are a thousand caveats to it.
Step one is where are your backups going to go. This can be a simple NFS/SMB share on a local server, it can be an s3 endpoint, but seriously this is step 1. Backups are critical with longhorn. You will fuck up Longhorn - multiple times. Losing these backups means losing all configs to all of your pods, so step one is to decide on your stable backup location.
Now, read the Longhorn install guide: https://longhorn.io/docs/1.9.0/deploy/install/. Do not skip reading the install guide. There are incredibly important things in there that I regretted glossing over that would have saved me. (Like setting up backups first).
The way I use longhorn is to create a PV in longhorn, and then the PVC (you can look up what both of these are later). Then I use Helm to set what the PVC name is to attach it to my pod. Try and do this with another sample pod. You are still not ready to move production things over yet, so just attach it to nginx. exec into it, write some data into the pvc. Helm uninstall. See what happens in longhorn. Helm install. Does your PVC reattach? Exec in, is your data still there? Learn how it works. I fully expect you to ping me with questions at this point, don't worry, I'll be here.
Longhorn will take time in learning, give yourself grace. Also after you feel comfortable with it, you'll need to start moving data from your old docker setup to Longhorn, and that too will be a process. You'll get there though. Just start with some of your lower priority projects, and migrate them one by one.
After all of this, there is still more. You can automount smb/nfs shares directly into pods for media or anything. You can pass in GPUs - or I even pass in some USB devices. You can encrypt your longhorn things, you can manage secrets with your favorite secret manager. There's thousands of things you'll be able to do. I wish you luck, and feel free to ping me here or on Matrix (@scrubbles@halflings.chat) if you ever need an ear. Good luck!
Yeah with Amazon's sheer size this has definitely been done before, curious what limits op is going to hit. My guess is they have a quota for submissions, and they'll be banned from submitting tickets.
I mean go for it? They literally can't do anything, you might as well complain that fire is hot though. It's part of being in the Internet. They provide safety gloves, via VPCs and firewalls, but if you choose not to use them then.. yeah I mean youre probably gonna get burned
115
Striking New York Times tech workers ask people not to play Wordle or other NYT games
(www.polygon.com)
206
Striking New York Times tech workers ask people not to play Wordle or other NYT games
(www.polygon.com)
Scrubbles' Guide to Trains in Satisfactory
Hello all, I was in a stream earlier today where I was watching Satisfactory, and realized that trains are pretty nuanced in Satisfactory, so I decided to write a quick guide on some of the ways I build out my rail network. For reference, my last build had over 80 train lines and well over 200 running trains at any moment.
Disclaimer: There is absolutely no right or wrong way to play Satisfactory. Everything below is my own personal preference that I have found works for my builds, but please don't take it as I'm saying it's the best way. Experiment and try things out!
Train Building
Each of my trains now is pretty standardized in length. I've found that this is the best way to balance cases where I run out of space on a train. The consist is:
| < Engine | < Engine | 10 x Cars | Engine > |
I've tried shorter ones, but what happens is when you run out of space you have to find each stop and add a station to it. I've also done 20 car trains. While fun, later in game they rubber-band a lot, and also lugging 20 cars up the hill to red forest takes A LOT of power. So I standardized on 10, and it's been a good mix. If I run out of space, usually that means I can add another station.
Track Layouts
The Mainline
My mainlines consist of 4 tracks, with 2 in each direction. This follows the British Network Rail standard, which I have found to be the best in game. Why two tracks? Well, one it looks really cool. 2, it has a ton of capacity. However the biggest one is that I have, just like in the UK, fast and slow tracks. The inside tracks are my "fast" tracks. I reserve these for trains going far distances, where they don't want to stop every 100m just to wait for some branch train cross over. They should maintain speed as much as possible. The outer tracks then are reserved for those branch lines.
In the UK, naming a track "Up" usually means towards London, and "Down" means away from London. Taking that to here, my "Up" tracks mean heading towards the Hub, and "Down" means heading away. So "Up Fast" is the fast track towards the Hub.
Secondary Lines
Of course, towards the end of those lines, or just where natually it's obvious, I will split those into two secondary lines. Splitting off to large areas or other factories this is a good way to maintain the level of trains on each of the 4 track mainlines.
Branch Lines
These are few and far between, but sometimes I do need just a random line that splits off to go to a resource node that's out of the way. For these I will take a single branch line out, and this will be the only time I have trains running in both directions on the same line. These lines usually have 1, or at max 2 trains on a single line, with enough space for passing at the loop at the end. The end of branchlines usually looks like:
------\---| Station-------------------------- | ----\ <- Train 1 filling at station
\ |
\-----------------------------------------/ <- Siding where train 2 can wait without blocking the exit
Building perfect curves
Making curves and straight lines can be a real pain when you're getting started. I want to write it down, don't spend time making your curves perfect. Make your straight tracks first, then connect your curves and let the game handle the spline for you. Like this:
This way you can always have sweet 90 degree or S turns.
Signalling
Now, with a complex network like this, signalling gets to be incredibly important. Because of this, here's a quick guide on how I make signals, and overall how I lay my tracks.
Block Signals
Taking what we had before, let's add some signals. I've added a double track with one line meant to go in each direction here. Note that there are right now, 6 different blocks in this image
Do you see them all? Let me highlight them.
So in this case, Block signals work perfectly fine. Block signals are the base signal type. They are "dumb" signals, purely saying "It is safe to enter into the block I am in front of." So on the curve of the right track it is green, if a train came up to it, yes, it is safe to move into that block. The one after it is blinking Yellow because well, there's no end to the block, so the train would stop.
So to recap. Block signals are dumb. Just binary yes it's safe to move in or not.
Let's add a switch here though. Let's assume these are all block signals. I colored out the signal at the beginning of our switch. Let's assume it's a block signal. What would it show?
Right now, if everything was a block signal, it would show green. That's because right now, the block is empty and it is safe for any train to move into the block. For many intersections, this can be fine. However, there's a pretty big issue with it.
What if there's a train right after that signal? If the next block is blocked, what would that signal do? See my crudely drawn train here:
Well, we know the second signal would be red - because there's a train in it obviously, so no other trains could move in. What would the original first signal be though? Well, since it's safe to move into our intersection, it would be green. However since it is not safe to move into the next block now we have a train in the middle of our intersection waiting for the next block to become clear, and in the meantime if another train came along, it would have to stop and wait for the entire line to clear out first.
That's not great, we have a lot of material to move! So, how can we keep this intersection clear to allow other trains by?
Path Signals
Path Signals are just slightly different. Path signals tell an upcoming train if it is not only safe to move into the next block, but if it is safe to move into the following block as well. So going back to the diagram, if we swap out that first signal for a path signal, here's what it would do:
Note that now the train waits at the signal before ever entering into the intersection. There is no safe path into the next block, so the Path signal will be red until the train ahead has cleared. This allows our trains coming in the opposite direction to safely pass by without worrying.
These concepts will expand out, and as your train network grows so do your intersections. It is crucial if you want a full train network that you understand these concepts. With these two simple tools, you can build out incredibly complex systems.
Building out parallel lines
Another question I've received is how do I make nice clean parallel tracks at great distances? The answer is I have a blueprint which is just the "pillar" itself, and it has "dangling" tracks out in front of it.
This allows me to "snap" my tracks together by placing a pillar out in front, snapping the tracks together, then deleting the dangling ones in front of it. For perfect straight lines you can see I have foundations in the blueprint too that are purely used to help snap the next blueprint to. I zoop a foundation out in front, snap the next pillar, snap the rail lines, then remove the foundations and the dangling rail lines. I then extends the pillar down to the ground.
How do I "split" trains on tracks?
I don't. So this question has come up a few times, if I have 4 tracks how do I prioritize trains on separate tracks? The answer is I don't really. What I do is when I build a station out in the middle of no where I make a concious decision on which of the 4 tracks I want to hook it up to. Do I want it on the fast line or the slow line? That will determine the train's path for the entire route, if it takes the inner or outer lines. Because of this, the fast and slow tracks never connect. Once a train is on the fast or slow track, that's it's path. The only place where these two parallel tracks meet is at the Hub, where each station branches to both the fast and the slow tracks. That just makes it easier for me to keep building in the field. If you can decipher it, this is how my Hub is laid out:
Note how each station branches off to both fast and slow lines. This is different then in the field where it chooses only fast or slow.
For those studying - also note that is one giant block (for most of the image). Each station has a Path signal, and at the end of that are the block signals. The train will leave the station only when there is a safe path out to the mainline.
More to come
I'm sure I'll have more to add, but this is a good primer on trains in Satisfactory. Satisfactory really does have a model train simulator baked right in. For me, this is a very fun part of the game, and I have spent hundreds of hours just building trains. They add a great dynamic to the game, and really do let you build huge workloads. Remember that adding things to a train is a lot less graphics load on your machine too, compared to hundreds of kms of conveyor belts, so there's a performance boost as well. In conclusion, I'll leave you to some of my favorite train screenshots:
Inspired by Paddington Station
Carrying the Mainline high above the world hole
Alternate Angle:
Rush hour at the mainline crossover at Rocky Junction
We named this area "Konpeki Plaza", in the downtown of our cyberpunk city. Trains would roll through a few times a minute.
I'm honestly shocked it took this long tbh. It's obviously a liability, the only question is what site is going to be sued into oblivion first, and a lawsuit would name everyone in the chain, from the site hosting it, to the cloud provider with the data on it, to the card processors. Whoever loses will be "made an example of" too, more than likely shuttering the doors of the site.