A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you’d prefer to keep out of more focused work-related channels. Archive: https://archive.sweetops.com/random/
i just used this to tighten a bolt at the back of my engine and i dont think ive ever felt more devops
Targeting 4:33 p.m. EDT today for Falcon 9’s launch of Crew Dragon with @NASA> astronauts on board. Teams are closely monitoring launch and downrange weather → http://spacex.com/launches <https://pbs.twimg.com/media/EZBpEteWkAAno8X.jpg
live feed of the spacex launch… https://www.youtube.com/watch?v=Aymrnzianf0
Join us on May 25, 2020 at 1:00 pm EST for ShipIt! presents How Shopify Uses Nix, a discussion about how Shopify is using Nix to rebuild our developer tooling with Burke Libbey. Please register. Over the past year and a bit, Shopify has been progressively rebuilding parts of our developer tooling with Nix. I initially planned to write about how we’re using Nix now, and what we’re going to do with it in the future (spoiler: everything?). However, I realize that most of you won’t have a really clear handle on what Nix is, and I haven’t found a lot of the introductory material to convey a clear impression very quickly, so this article is going to be a crash course in what Nix is, how to think about it, and why it’s such a valuable and paradigm-shifting piece of technology. There are a few places in this post where I will lie to you in subtle ways to gloss over all of the small nuances and exceptions to rules. I’m not going to call these out. I’m just trying to build a general understanding. At the end of this post, you should have the basic conceptual scaffolding you need in order to think about Nix. Let’s dive in! What is Nix? The most basic, fundamental idea behind Nix is this: Everything on your computer implicitly depends on a whole bunch of other things on your computer. All software exists in a graph of dependencies. Most of the time, this graph is implicit. Nix makes this graph explicit. Four Building Blocks Let’s get this out of the way up front: Nix is a hard thing to explain. There are a few components that you have to understand in order to really get it, and all of their explanations are somewhat interdependent; and, even after explaining all of these building blocks, it still takes a bit of mulling over the implications of how they compose in order for the magic of Nix to really click. Nevertheless, we’ll try, one block at a time. The major building blocks, at least in my mental model of Nix, are: The Nix Store Derivations Sandboxing The Nix Language. The Nix Store The easiest place to start is the Nix Store. Once you’ve installed Nix, you’ll wind up with a directory at /nix/store, containing a whole bunch of entries that look something like this: 3mfcmgmpcqjajpdhfh8pdazmmd4vskns-nix-2.3.3-man/h9bvv0qpiygnqykn4bf7r3xrxmvqpsrd-nix-2.3.3/nrb3rkvwz114053yh00r7p2dlc9igp03-nix-2.3.3.drv This directory, /nix/store, is a kind of Graph Database. Each entry (each file or directory directly under /nix/store) is a Node in that Graph Database, and the relationships between them constitute Edges. The only thing that’s allowed to write directories and files into /nix/store is Nix itself, and after Nix writes a Node into this Graph Database, it’s completely immutable forever after: Nix guarantees that the contents of a Node doesn’t change after it’s been created. Further, due to magic that we’ll discuss later, the contents of a given Node is guaranteed to be functionally identical to a Node with the same name in some other Graph, regardless of where they’re built. What, then, is a
Nix is so freaking cool. I wish I had the time to really get into it more….
https://twitter.com/castrojo/status/1263173051333709827 by the way this is from today’s k8s office hours
This lady dog was listening in on the #Kubernetes office hours but didn’t really have an opinion on anything until we got talking about Vertical Pod Autoscalers, then all of a sudden she was all in. Even dogs can learn from our community. https://pbs.twimg.com/media/EYew2KjX0AIRAeT.jpg
All changes are welcome as long as no code is involved. If you run into any bugs, please file an issue and explain how that was even possible.
The best way to write secure and reliable applications. Write nothing; deploy nowhere. - kelseyhightower/nocode
[https://desertedisland.club/> @Erik Osterman (Cloud Posse) oooohhhhhh my god, tell me cloud posse was represented. Hahah. This is awesome. I missed it, but hopefully there’s more legit engineering meetups like this via video game platforms. </i](https://desertedisland.club/)
devops in a nutshell https://www.youtube.com/watch?v=AbSehcT19u0
Create new iCloud synced inboxes on-demand without having to sign up for new accounts or needing to remember a new password in one click of a button with Binbox. You can have a virtually unlimited number of inboxes which can be used with services that you don’t want to share your “main” email addre…