If you don’t mind me asking, what made you go with VoidAuth vs Authelia or something else entirely?

I’m in a similar boat as OP and while VoidAuth looks very promising I’m put off a little by the young age and size of the project.

This fixes a lot of the major pain points that pushed me to using Typst in the first place.

It’s too late for me to come back but hopefully this makes someone else’s life a little easier.

Harper is great, but it only does English. Really wish their “extensible core” was extended to other languages sometime.

I assume you’ve used ESPHome for the firmware?

Did you have to mess around with deep sleep or is the battery + solar combo so overkill that it doesn’t matter?

Anyways very cool project. Thanks for sharing

Got it working thanks to your troubleshooting tips now. Also found a very neat way to handle secrets from another comment.

I tend to run a DB instance per service as that makes backup restoration much easier for me. An idle postgres sits at around 50MB which is a cost I’m willing to pay.

Thank you again for your help :)

Managed to get it working by passing in env vars from a secret now.

ArgoCD has a really handy web UI that allows you to quickly see what kind of resources get deployed.
Especially for learning k8s I found that much easier to visualize than raw kubectl outputs.

Passing in the secrets once via the global: section is very neat. Got it working now with a few of the other tips and stole your trick for my secret handling. Thank you :)

Did you also have to set all these env vars by hand?
I am wondering if it might have something to do with rendering Helm Charts under ArgoCD.

I’ll give it another try with your recommendations.

And should I get it working finally, I will obviously switch back to using Secrets.
I only removed them to reduce possible points of failure.

As for blueprints, that’s a task for future me xD

I’ve written my bachelors thesis with it.

You won’t get any official pre made templates for your thesis (yet) and if you require some obscure notation you probably won’t find a ready made package for it.

For my purposes I only needed some pictures and code blocks which works perfectly fine.

Also typst’s show rules are awesome.

Same here. Literally just set it up and now this.

I hope the author will roll this back or someone else makes a fork. I don’t want to immediately switch technology to XMPP/Matrix/… and have to do it all over again.

Also the normal and rpi versions are two completely independent implementations of the same software. So now the LLMs have twice the maintenance load.

I didn’t diff the two files but even the startup and control code appears to be custom for each version.

Since projects of the same language often use the same tooling this makes it easier to clean up the whole directory by running something like this:

for d in ./*/ ; do (cd "$d" && somecommand); done

somecommand could be cargo clean if you’re in the Rust directory for example.

Depends on the exact system but there will be a method to switch to a newer release channel without reinstalling. Rinse and repeat every x years.

Interesting, GPG has been working just fine for me so far.

My main issue with it remains that barely anyone else uses GPG.

Are the common-controls determined per user?

If yes, that would be awesome.

Not just on the web. I’ve previously used it to embed a short clip in a presentation.

The nice thing is that it doesn’t do a massive screencap but only captures the text. This way the replay will be freshly rendered at native resolution.

My motivation for using NixOS is maintenance. I’ve been running 2-3 personal Linux computers for the last decade, with one of them being a server.

To get stuff like services working with each other you sometimes need to make small changes to the config files of some services. The issue for me especially with the many services running on the server is coming back to a broken/misbehaving machine after 4+ months and now having to research what changes I made long ago and where those config files are buried.

Making the change and testing it would likely take less than 5 minutes if you had every detail you need fresh on your mind.

I simply don’t have the mental capacity to remember all that stuff after months of working on other things. Especially if you’re coming back to something broken this is a really annoying position to be in.

You want the fix now but have to start by looking up docs and trying to figure out what past-self did to get you into this mess, or to find out what has changed since then.

At some point I had enough and was either going to teach myself some sort of personal changelog / documentation system, or learn a new declarative configuration system.

Huge respect for anyone who can keep all this info in their mind and to those that meticulously update their own documentation, but I lack the discipline to do so in the heat of battle and will easily miss things.

Since then any system that I will have to maintain myself has been using some form of declarative management. It keeps all configuration accessible and organized in one place, so I don’t have to go digging for the correct file paths. It self updates so that even when I go back and forth during testing I won’t miss updating my standalone docs.

And NixOS brings this to my whole system. No old programs lying around because you forgot to uninstall them and have now forgotten about it. Same thing with pinned package versions that then wreak havoc once they’re incompatible with the updated rest of the system. It even configures my goto tools (shell, editors, etc) to my personal liking when I set up a new machine.

Its not the first declarative system and probably won’t be the last one I will use, but for now it really makes my life noticeably easier.

I get that this seems very intimating, but if you’ve ever used more than three programming languages in your life, I believe you won’t have much to learn.

I can mimic the syntax and I very roughly understand how the import system works. But I don’t know Nix! Yet I haven’t had any trouble language wise over the last few years.

In my experience most of the “code” you write is package names and those can be copied from search.nixos.org.

In that sense I’m effectively using it as a markup language and I don’t think anyone has ever gotten discouraged by having to “learn” YAML, just so they can write a config file for some piece of software they want to use.

Something that I would take as discouragement is the state of the documentation. It has been improving to a usable level in some areas but other areas are heavily outdated or just plain missing.

Thanks for the heads up. I have an ESPHome device with a display where I’ve replicated the HA look and feel. Guess I’ll have to update that now

While I fully agree with the opt-in sentiment, 95% of all core integrations are likely “inactive bloatware” on your instance, yet I don’t see anyone complaining about that.

Last time I checked we were at around 1500 core integrations on the search page.