Rin
/
snek-tech-blog
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

update styling for us + add last mod time

feature/font
AtelierSnek 2022-11-06 10:51:22 +11:00
parent b87ee5c039
commit 86f87f4344
5 changed files with 47 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
assets/css/custom.css
View File

@ -64,7 +64,7 @@
body a, body button {
transition-duration: 250ms;
}
/* TOOLTIPS */
.tooltip {
position: relative;
display: inline-block;
@ -104,3 +104,12 @@ body a, body button {
background-color: rgba(var(--color-neutral-800),var(--tw-bg-opacity));
color: rgba(var(--color-secondary-400),var(--tw-text-opacity));
}
/* BLOCKQUOTES that don't suck */
.prose :where(blockquote p:first-of-type):not(:where([class~=not-prose] *))::before {
content: none;
}
.prose :where(blockquote p:last-of-type):not(:where([class~=not-prose] *))::after {
content: none;
}

2
config/_default/config.yaml
View File

@ -6,7 +6,7 @@ theme: blowfish
baseURL: "https://rin.systems/"
defaultContentLanguage: en
enableRobotsTXT: true
paginate: 20
paginate: 10
summaryLength: 100
buildDrafts: false
buildFuture: false

2
config/_default/params.yaml
View File

@ -32,7 +32,7 @@ homepage:
showMoreLinkDest: /posts
article:
showDate: true
showDateUpdated: false
showDateUpdated: true
showAuthor: true
showBreadcrumbs: true
showDraftLabel: true

15
content/pay-transparency.md
View File

@ -1,6 +1,7 @@
---
title: "Pay Transparency"
date: 2022-11-01T11:11:29+11:00
lastmod: 2022-11-06T10:45:00+11:00
draft: false
summary: "This page lists every job we have ever held in tech, inspired by Xe’s salary transparency page."
showSummary: true
@ -32,10 +33,10 @@ This page is typically updated whenever we:
- other unspecified things happen.
## Your Turn!
**(Ashe)** Please consider also publishing your salary/pay data. The more information is out there in the open,
the better equipped everyone is to handle pay negotiation and the more likely we are to ensure that everyone is paid fairly.
**(Selene)** By sharing this information publicly and unabashedly, we can end the stigmas around discussing pay
and renumeration. These stigmas serve only to leave people in the dark and unable to argue for their own worth.
**(Octavia)** As they say, the light of day is the best disinfectant.
> **(Ashe)** Please consider also publishing your salary/pay data. The more information is out there in the open,
> the better equipped everyone is to handle pay negotiation and the more likely we are to ensure that everyone is paid fairly.
>
> **(Selene)** By sharing this information publicly and unabashedly, we can end the stigmas around discussing pay
> and renumeration. These stigmas serve only to leave people in the dark and unable to argue for their own worth.
>
> **(Octavia)** As they say, the light of day is the best disinfectant.

50
content/posts/server-build.md
View File

@ -1,6 +1,7 @@
---
title: "Our Home Server Build-Out Log Part 1: Speccing It Out"
date: 2022-10-31T17:00:00+11:00
lastmod: 2022-11-06T10:45:00+11:00
draft: false
showSummary: true
summary: "We've wanted to build a home lab for a long time. Here's how it went."
@ -15,12 +16,12 @@ series_order: 1
We've wanted to build a home lab for a long, long time, but never got around to it.
**(Selene)** However, a certain someone was complaining about disaster recovery and migrating workloads to us,
and that turned out to be just the push we needed to get this rolling.
> **(Selene)** However, a certain someone was complaining about disaster recovery and migrating workloads to us,
> and that turned out to be just the push we needed to get this rolling.
Since we also want to do more blogging and community contribution, why not make this the inaugural post on our new blog?
**(Lorelai)** So, let's get this show on the road, shall we?
> **(Lorelai)** So, let's get this show on the road, shall we?
## The Use-Case
@ -45,12 +46,12 @@ After deliberating on it for a while, we decided on the following:
### But Why?
**(Selene)** I'm no techie, but this all seems rather excessive for a home server. Especially compared to people we know.
**(Ashe)** You're not wrong there, Selene. I could wax lyrical about how I want this server to last a long time and be
useful for many different things and so on and so forth, but if we're being honest, the main reason is "Tech shiny!"
**(Tammy)** So the same reason we've always gotten high spec PCs, really.
> **(Selene)** I'm no techie, but this all seems rather excessive for a home server. Especially compared to people we know.
>
> **(Ashe)** You're not wrong there, Selene. I could wax lyrical about how I want this server to last a long time and be
> useful for many different things and so on and so forth, but if we're being honest, the main reason is "Tech shiny!"
>
> **(Tammy)** So the same reason we've always gotten high spec PCs, really.
## Fulfilling the Spec
@ -73,10 +74,10 @@ the ZFS instance properly.
The goal is to have a scaleable template that can be expanded without breaking the bank each time,
while maintaining favourable failure characteristics. We'll budget out 3000 AUD for each expansion.
**(Doll)** That sounds like a lot, Miss...
**(Ashe)** It's a good chunk, yes. But this should, ideally, only happen every few years, so we can amortise this
over the life of the storage.
> **(Doll)** That sounds like a lot, Miss...
>
> **(Ashe)** It's a good chunk, yes. But this should, ideally, only happen every few years, so we can amortise this
> over the life of the storage.
We have 12 3.5" slots in our 3U compute case, and most storage arrays are either 24 or 36 bay, so planning around
12 unit slices seems logical.
@ -183,13 +184,13 @@ We don't *need* 10GbE for our management network, but this allows us to build th
upgrade to 2 ✕ 40GbE later, which may be what we end up doing. Notably, this leaves us without separate management and
data interfaces.
**(Selene)** Is that a problem?
**(Ashe)** Not really, no. It makes securing the network *slightly* trickier as we can't airgap the management network,
but it's not the end of the world. We intend to get a PCIe Ethernet card at some point anyway, so this'll
be temporary.
**(Octavia)** Famous last words.
> **(Selene)** Is that a problem?
>
> **(Ashe)** Not really, no. It makes securing the network *slightly* trickier as we can't airgap the management network,
> but it's not the end of the world. We intend to get a PCIe Ethernet card at some point anyway, so this'll
> be temporary.
>
> **(Octavia)** Famous last words.
New from Newegg, this sets us back ~1100 AUD.
@ -211,8 +212,11 @@ There are two ways we can estimate how much RAM we'll need.
* We should be able to halve or even quarter this and not encounter bottlenecks.
* We'll initially provision 32GB, and adjust as necessary.
4. Modded Minecraft Server
* 16 - 32 GB is the rough ballpark for good performance with 8 - 16 players
* This is likely overkill for our server, so we can dial it back to 12GB with some GC tuning on the server end
* 16 - 32 GB is the rough ballpark for good performance with 8 - 16 players.
* This is likely overkill for our server, so we can dial it back to 12GB with some GC tuning on the server end[^1].
[^1]: GC tuning for Minecraft is its own beast, and one we could probably write a decent chunk about. Maybe a topic for
a future blog post?
So that totals up to 8 + 2 + 32 + 12 = 54 GB.
@ -252,4 +256,4 @@ With all that decided upon, ordered, all we have to do now is wait for it to arr
Join us again next time for the actual build log!
**(Doll)** This one is super excited to see Miss' build the nyoomy server!
> **(Doll)** This one is super excited to see Miss' build the nyoomy server!