flexiondotorg

Author here. Yes, another AI commit generator - I know, I know.

I built faff after GitKraken's AI wouldn't generate proper conventional commits despite custom prompts. Local Ollama + qwen2.5-coder models work surprisingly well for conventional commits. Simple shell script, no cloud APIs. https://github.com/wimpysworld/faff

Thanks for the kind words, I'll pass them along to Ana

I mostly run NixOS but do work on macOS occasionally and being to bring all my familiar home environment, configuration, tools and a multitude of project specific development shells is a huge time saver.

Sorry about that. Just checked. This is due to our phased rollouts which are currently 50/50.

We're just ramping 0.14 up to 100%. So please try again in about 10 mins

Passing through a GPU to a kernel in a VM requires fiddling with SR-IOV and IOMMU, which also requires your hardware is compatible. Often hardware is not compatible, either by design because these features are artificially reserved for "enterprise" models or due to accidental IOMMU group conflicts on lower priced motherboards.

As containers share the host kernel, these issues do not arise and hardware acceleration is trivial.

This OBS Studio Portable container is built with Ubuntu, because Ubuntu is one of the supported Linux targets by upstream OBS. The OBS Studio Portable container is a ready-to-run, batteries included turn-key solution.

I am a NixOS user and nixpkgs maintainer. I've been working on adding more OBS plugins to nixpkgs and fixing OBS Studio in nixpkgs, but it needs more work:

- For me, it is missing some plugins I rely on and some of the OBS plugins in nixpkgs do not work. I am actively working on this.

- FDK ACC doesn't work in OBS in nixpkgs and the ffmpeg version is not fully API compatible with OBS, meaning some presets do not work. On my list to fix.

- CEF in nixpkgs is not ABI compatible with OBS and cause OBS to segfault when authenticating Twitch. Again, on my list of things to fix.

I have a long history of building a custom OBS Studio on Ubuntu, so decided to make this OBS Studio container with my friends in the Universal Blue project, to get myself a complete OBS setup I can use on NixOS while I continue to work on OBS related fixes in nixpkgs :-)

That is a nifty solution

I stream to Twitch and also to an unlisted YouTube stream., using livepush.io. I do this so I have an archive of my live stream on YouTube that I can easily publish after 24 hours :-)

I've been streaming this way for a while now.

Yes, you can dual stream.

- I do this using livepush.io. So one stream out to livepush and they push to multiple services. - However you could run multiple instances of this container and have each stream to a different service. For example one container being the main streaming setup that streams to Twitch but also has NDI or Teleport output that can then be ingested via a second instance of this container that streams to YouTube.

Using this is KVM is technically possible but you'd lose a load of the benefits of running in a container, such as hardware acceleration and seamless integration with your host.

Can ChromeOS running Podman and Distrobox? If so, it should work fine.

I have an interest in Linux, so making a Windows build is not something I'm interested in but I see no reason why it couldn't be done.

But you raise a good point about compatibility, everything in this container is built from source so everything is API/ABI compatible since the same toolchain is used throughout.

Glad you like it :-)

Delighted to finally see FlakeHub out in the wild. Keen to answer questions, but if you'd like a direct community with the DetSys team we invite you to join us on Discord: https://discord.gg/invite/a4EcQQ8STr

Yes, macOS is supported. X86_64 and Apple Silicon

Zero to Nix introduces Nix, not NixOS the operating system. So, there's not really a need for screen shots as Zero to Nix it teaching how best to install and use Nix on any Linux or macOS. For that, code snippets are convenient I think.

I like the idea of having a flow through, at least, some of the concepts in the order they should be introduced.

I like the idea of a NixOS section.

Closing in on 20 years of existence doesn't really qualify for fad

I'm just starting a serious learning journey with Nix after flirting with the idea for a few years. Mostly because I find myself endlessly working on tooling to support the projects I work on that Nix already does extremely well.

The feature I am most sold on is the ability to invoke clean complex development environments, that bring themselves to existence automatically as I traverse directories. If you work in code or in DevOps, Nix is totally worth a look.

It provides a complete, familiar, desktop environment that can be used for basic desktop computing. I've been using Ubuntu MATE on the Pi to introduce my daughter to computing for several years now.

But, it is probably of more interest to makers and device hackers who want to target Ubuntu for their projects. You can prototype homebrew ARMv7 or ARMv8 based IoT devices in a comfortable desktop environment, including building and testing your apps as snaps (https://snapcraft.io). The full Ubuntu archive is available to you.

For hobbyist projects, you can stick with Ubuntu MATE for "deployment", even with the option to disable the X11 display server if it not an application requirement. But, if you have something more professional in mind then the applications and snaps you've prototyped with Ubuntu MATE can be used with Ubuntu server or Ubuntu Core (https://www.ubuntu.com/core) on one of the ARM-based reference platforms.

https://www.youtube.com/watch?v=mGcHNnI2mh4

I've also found distributing Python apps that require a significant Python stack suit snaps very well. My podcast publishing utility is only available as a snap for this very reason.

https://bitbucket.org/flexiondotorg/podpublish

No problem at all, snaps will happily co-exist alongside debs or any other package format for that matter :-)

Snap has a feature called content sharing which enables a snap to connect to assets (which can be data, shared objects, anything) in another snap.

Decide for yourself, here are links to the LibreOffice snapcraft.yaml and the Debian packaging. Snaps are far, far simpler.

## Snapcraft

https://git.launchpad.net/~bjoern-michaelsen/df-libreoffice/...

## Debian

https://anonscm.debian.org/git/pkg-openoffice/libreoffice.gi...