Update dates and add new streaming post
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
+++
|
||||
title = "CRIU Experiments"
|
||||
date = 2026-03-31
|
||||
date = 2026-06-30
|
||||
description = "Experimenting with CRIU"
|
||||
draft = true
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
+++
|
||||
title = "Homelab - IPv4 Expose"
|
||||
date = 2026-02-23
|
||||
date = 2026-04-04
|
||||
description = "How I expose my IPv6 only Homelab for IPv4 clients"
|
||||
draft = true
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
+++
|
||||
title = "Homelab - Monitoring"
|
||||
date = 2026-02-16
|
||||
date = 2026-05-04
|
||||
description = "My current homelab monitoring setup"
|
||||
draft = true
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
+++
|
||||
title = "Homelab - Overview"
|
||||
date = 2026-02-16
|
||||
date = 2026-05-04
|
||||
description = "A quick and rough overview of my Homelab setup"
|
||||
draft = true
|
||||
|
||||
@@ -9,6 +9,32 @@ categories = ["Homelab"]
|
||||
tags = ["Homelab", "Ceph", "Vault", "Nomad", "Consul"]
|
||||
+++
|
||||
|
||||
{% mermaid() %}
|
||||
block
|
||||
columns 3
|
||||
nomad:3
|
||||
ceph consul vault
|
||||
{% end %}
|
||||
|
||||
{% mermaid() %}
|
||||
architecture-beta
|
||||
group homelab(cloud)[Homelab]
|
||||
group cloud(cloud)[Cloud]
|
||||
|
||||
service db(database)[Database] in homelab
|
||||
service disk1(disk)[Storage] in homelab
|
||||
service disk2(disk)[Storage] in homelab
|
||||
service server(server)[Server] in homelab
|
||||
|
||||
service proxy(server)[Proxy] in cloud
|
||||
|
||||
service internet(internet)[Internet]
|
||||
|
||||
db:L -- R:server
|
||||
disk1:T -- B:server
|
||||
disk2:T -- B:db
|
||||
{% end %}
|
||||
|
||||
The goal of this post to give a quick high-level overview of my current Homelab setup, to avoid having to re-explain everything on every following post that focuses on one part of it.
|
||||
|
||||
## Hardware
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
+++
|
||||
title = "Quickfacts - Part 1"
|
||||
date = 2026-03-01
|
||||
date = 2026-05-01
|
||||
description = "The first part of a series about my Quickfacts project"
|
||||
draft = true
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
+++
|
||||
title = "Quickfacts - Intro"
|
||||
date = 2026-03-01
|
||||
date = 2026-05-01
|
||||
description = "An introduction to my Quickfacts project"
|
||||
draft = true
|
||||
|
||||
|
||||
28
content/streaming/index.md
Normal file
28
content/streaming/index.md
Normal file
@@ -0,0 +1,28 @@
|
||||
+++
|
||||
title = "Streaming setup"
|
||||
date = 2026-03-15
|
||||
description = "Custom streaming setup to complement teamspeak"
|
||||
draft = true
|
||||
|
||||
[taxonomies]
|
||||
categories = ["Homelab"]
|
||||
tags = ["Homelab"]
|
||||
+++
|
||||
|
||||
## Motivation
|
||||
Recently my friends and I decided to move away from discord as much as we can.
|
||||
The voice stuff was easy, just self host a Teamspeak3 instance on my Homelab and you are good to go
|
||||
(with arguably better results).
|
||||
|
||||
However we often had screenshares running in our discord, especially when everyone is just chilling
|
||||
in the same voice channel and someone shares their game/whatever in case anyone wants to check in.
|
||||
But as the experienced teamspeak user might be aware, TS3 does not support screen sharing or anything
|
||||
the like natively.
|
||||
|
||||
## OvenMediaEngine + OBS
|
||||
Luckily I found OvenMediaEngine, which is an entire software setup to basically host your own streaming
|
||||
platform. This is obviously overkill for our goal, but works better than I would have expected at first.
|
||||
|
||||
## Teamspeak3 Plugin
|
||||
To make the setup for my friends easier and to add some form of security/authentication, I wrote a small
|
||||
teamspeak plugin, which generates the credentials and urls needed to both stream yourself and watch streams.
|
||||
@@ -1,7 +1,7 @@
|
||||
+++
|
||||
title = "Homelab - UDMPro"
|
||||
date = 2026-02-16
|
||||
description = "How I expose my IPv6 only Homelab for IPv4 clients"
|
||||
date = 2026-03-04
|
||||
description = "Documenting my configuration for the UDMPro"
|
||||
draft = true
|
||||
|
||||
[taxonomies]
|
||||
@@ -9,11 +9,9 @@ categories = ["Homelab"]
|
||||
tags = ["Homelab", "IPv4", "IPv6"]
|
||||
+++
|
||||
|
||||
## Existing stuff
|
||||
Router IPv6: 2001:4dd5:ae46:0:76ac:b9ff:fe3e:f163
|
||||
|
||||
Default network: 2001:4dd5:ae46:80::/64
|
||||
Server-Cluster network: 2001:4dd5:ae46:81::/64
|
||||
## Old Setup
|
||||
Previously I had my ISP provided Router setup for just the LAN stuff, so no WiFi, no firewalling just acting in the dumbest way I could configure directly in the UI.
|
||||
My UDMPro was then the only downstream client connected to the Router and was the real router for my network.
|
||||
|
||||
## New Setup
|
||||
Reconfigure the FritzBox:
|
||||
|
||||
Reference in New Issue
Block a user