hellricer

#!/bin/sh

echo "# 24-bit (true-color)"
# based on: https://gist.github.com/XVilka/8346728
term_cols="$(tput cols || echo 80)"
cols=$(echo "2^((l($term_cols)/l(2))-1)" | bc -l 2> /dev/null)
rows=$(( cols / 2 ))
awk -v cols="$cols" -v rows="$rows" 'BEGIN{
    s="  ";
    m=cols+rows;

danbst

{ config, pkgs, lib, ... }: {
  imports = [
    (import <nixpkgs/nixos/modules/system/etc/etc.nix>)
  ];

  options.system.build.etc = lib.mkOption { type = lib.types.package; };
  options.system.activationScripts.etc =
    lib.mkOption { type = lib.types.unspecified; };

  config = {

astutecat

#!/bin/sh
set -e

root_disk() {
    diskutil info -plist /
}

apfs_volumes_for() {
    disk=$1
    diskutil apfs list -plist "$disk"

networkingcat

blueprint:
  name: Yet Another Motion Automation
  description: >
    # YAMA V10


    Turn on lights or scenes when motion is detected. 
    
    Four different scenes can be defined depending on time of day.
    

nepozs

Getting the Raspberry Pi Camera to Work on HASSOS

Enabling the Raspberry Pi camera on HASSOS installations is unfortunately not as simple as connecting the camera and configuring Home Assistant as described at https://www.home-assistant.io/integrations/rpi_camera.

For the camera to work at all, an alternate firmware needs to be loaded when the Raspberry Pi boots. On Raspberry Pi OS (and many others), the alternate firmware is included with the OS installation image, and switching to the alternate firmware is accomplished by running raspi-config and selecting "Enable Camera" from the menu. HASSOS does not include either the alternate firmware or the raspi-config program, so all of the steps need to be done manually.

The steps below attempt to describe the steps that need to be performed. They have worked for me on a Raspberry Pi 3B+ running HASSOS 4.11 through 4.15. If you have a different setup your mileage may vary (but hopefully you'll get enough hints from the below to get it working).

A Home Assista

byrongibson

# Edit this configuration file to define what should be installed on
# your system.  Help is available in the configuration.nix(5) man page
# and in the NixOS manual (accessible by running ‘nixos-help’).

{ config, pkgs, ... }:

{

################################################################################
# System 

PanAeon

{ config, pkgs, lib, ... }:
let
  cfg = config.services.btrbk;
  sshEnabled = cfg.sshAccess != [ ];
  serviceEnabled = cfg.instances != { };
  attr2Lines = attr:
    let
      pairs = lib.attrsets.mapAttrsToList (name: value: { inherit name value; }) attr;
      isSubsection = value:
        if builtins.isAttrs value then true

kaaquist

Podman with docker-compose on MacOS.

Podman an alternative to Docker Desktop on MacOS

Getting podman installed and started is super easy.
Just use brew to install it.

> brew install podman

Now since podman uses a VM just like the Docker Client on MacOS we need to initialize that and start it.

L3afMe

# Setup directories
__BASE_DIR="$HOME/Public"

## Config directory
export XDG_CONFIG_HOME="$__BASE_DIR/Config"

## Misc directories
__MISC_BASE_DIR="$__BASE_DIR/Etc"
export POWERCORD_DIR="$__BASE_DIR/Programs/powercord"
export GOPATH="$__MISC_BASE_DIR/Go"

acarril

For some reason, it is surprisingly hard to create a bootable Windows USB using macOS. These are my steps for doing so, which have worked for me in macOS Monterey (12.6.1) for Windows 10 and 11. After following these steps, you should have a bootable Windows USB drive.

1. Download a Windows disc image (i.e. ISO file)

You can download Windows 10 or Windows 11 directly from Microsoft.

2. Identify your USB drive

After plugging the drive to your machine, identify the name of the USB device using diskutil list, which should return an output like the one below. In my case, the correct disk name is disk2.