lexfrei

Claude Code Statusline with Real Usage Limits

Enhanced statusline for Claude Code that shows real quota usage from Anthropic API instead of estimates.

Features

• 🟢🟡🟠🔴 Rate indicators — compares usage% with elapsed time%
• 5-hour window — always shown with time remaining
• 7-day window — shown only when ≥70% used
• 60-second cache — avoids excessive API calls

kvaps

# Builds pkg
cd ./pkgs
git checkout release-1.9
make PKGS_PREFIX=ghcr.io/kvaps/talos PUSH=1 USERNAME=kvaps/talos PLATFORM=linux/amd64

# output would be:
# => pushing manifest for ghcr.io/kvaps/talos/base:v1.9.0-15-g45c4ba4-dirty@sha256:f3d0f691752e3158c4f36b05e4b5abad2e68437f0faa0928887e69e568ca364d

# Builds talos (with clustom pkgs)
cd ./talos

kvaps

#!/bin/sh

run(){
  name="$1"
  shift
  (
    set -x
    # defailt parameters
    fio -name="$name" -filename=$disk -output-format=json -ioengine=libaio -direct=1 -randrepeat=0 "$@" > results/$disk_dashed-$name.json
  )

Andor

local p = import '../../params.libsonnet';
local params = p.components.victoriametrics;

local k = import '1.21/main.libsonnet';

local vm = importstr 'data://victoriametrics/github.com/VictoriaMetrics/helm-charts/raw/347d4558d9c25cd341718bf5a2ee167da042c080/packages/victoria-metrics-cluster-0.9.6.tgz';

{
  local ns = k.core.v1.namespace,
  namespace::

cristiklein

#!/bin/bash

set -e

IMAGE_URL=https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img
IMAGE_FILE=$(basename $IMAGE_URL)

if [ ! -e $IMAGE_FILE ]; then
    wget $IMAGE_URL
fi

pytimer

Parse the kubernetes manifest in yaml or json, don't care a manifest type.

Examples:

package main

import (
	"bytes"
	"context"

vholer

#!/bin/bash

# Simple conversion script of ISO 9660 image into image based
# on ext2/3/4 filesytem. Completely unprivileged, without needing
# to mount both images. Free to use under Apache 2.0 License.
# 2020, Vlastimil Holer <vlastimil.holer@gmail.com>

set -e -o pipefail

TYPE=${TYPE:-ext2}

EddieIvan01

// +build darwin linux

package main

import (
    "os"
    "syscall"
    "unsafe"
)

gushmazuko

Proxmox VE Installation on Hetzner Server via Rescue System

Follow these steps to install Proxmox VE on a Hetzner server via the Rescue System. The Rescue System is a Linux-based environment that can be booted into to perform system recovery tasks. We'll be using it to install Proxmox VE.

In order to complete the process, it is indeed necessary to first boot into the Rescue System and then connect to it via SSH. This will allow you to run the commands for installing Proxmox VE. Here are the steps:

Starting the Rescue System

1. Log into the Hetzner Robot.
2. Under "Main Functions; Server" select the desired server and then open the tab "Rescue".

bmaupin

1. Change apiVersion from:

   - apiVersion: v1

   (or apiVersion: apps.openshift.io/v1)

   to: