ruffsl

joined 2 years ago
[–] ruffsl@programming.dev 1 points 4 hours ago

I think it stands for Managed Service Providers.

[–] ruffsl@programming.dev 3 points 1 day ago (4 children)

I'm still using an old UC Gateway, doubt my homelab will outgrow it.

 

How many folks already self-host UniFi on their own hardware vs native consoles?

Related Discussion:

 

A response to Drew Lyton’s "The Future is NOT Self-Hosted"


Related Discussions:

 

The future is community-hosted


Related Hacker News thread:

[–] ruffsl@programming.dev 8 points 3 weeks ago (4 children)

Looks like they introduce the use Traefik with NixOS here:

How does Traefik compare to a reverse proxy like Caddy?

 

Cross-posted from: https://programming.dev/post/33674513

Any general suggestions when getting started with headscale?

 

Sascha Koenig looks to have some quality deep guides around NixOS!

 

The idea behind the first requirement was that I want to be able to reduce the creation of the logo to a few simple parameters. Additionally, if I can generate the SVG files programmatically, I can programmatically generate the Branding Guide and Media Kit. I’m calling this approach “Branding as Code” (BaC)

That sounds neat, and quite in the spirit of Nix itself! This PR looks to be the work in progress mentioned:

[–] ruffsl@programming.dev 2 points 3 months ago

I'm not the original author, even with the YouTube title being as is, but what do you mean? Perhaps relying that the desired services exist as nix packages, or that nix packages have desired defaults or exposes desired config parameters?

There are two other nix media server config projects I can think of, but I think this approach mostly facilitates the install, but not the entire initial config setup, given that a lot of the stack's internal state is captured in databases rather than text config files. So simplifying the backup and restoration of such databases seems the next best thing to persist your stack configs with nix.