hermogenes

Incident Communication Guide

For Small Teams

Purpose

This guide defines when to declare an incident, who is responsible for communication, and how to communicate externally during an incident.

It also defines how to act technically during an incident, emphasizing mitigation over fixes to reduce risk and downtime.

willccbb

# train_grpo.py
#
# See https://github.com/willccbb/verifiers for ongoing developments
#
"""
citation:

@misc{brown2025grpodemo,
  title={Granular Format Rewards for Eliciting Mathematical Reasoning Capabilities in Small Language Models},
  author={Brown, William},

rafaribe

# $XDG_CONFIG_HOME/k9s/alias.yml
alias:
  sec: v1/secrets
  sm: monitoring.coreos.com/v1/servicemonitors
  ss: apps/v1/statefulsets
  udp: traefik.containo.us/v1alpha1/ingressrouteudps
  

magickatt

name: Validate Helm charts

on:
  push:
    branches: [ main, master ]
  pull_request:

jobs:
  validate:
    runs-on: ubuntu-latest

jgaskins

#!/usr/bin/env bash

# Install nginx ingress controller
# NOTE: This uses DigitalOcean. If you use another Kubernetes provider,
# substitute the appropriate command from here: https://kubernetes.github.io/ingress-nginx/deploy/#cloud-deployments
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.5.1/deploy/static/provider/do/deploy.yaml

# FOR DIGITALOCEAN DEPLOYMENTS:
export LB_HOSTNAME=example.com # Make this the DNS name that will point to your LB
export LB_NAME=my-lb # Give this a useful name to identify it on the DigitalOcean control panel

Paraphraser

Checking your Raspberry Pi's view of its power supply

Sometimes it seems like the first (and sometimes only) advice you get offered for almost any problem with a Raspberry Pi is "check your power supply". You think something like:

"hey, I'm using an official power supply sold as being matched with my Pi so how can there be any problem?"

You look up the specs then stick a controlled load across your supply and confirm that it can deliver the required number of Watts.

Yet your problems persist…

Phate334

version: "3"

services:
  janusgraph:
    image: janusgraph/janusgraph:0.6.2
    container_name: jce-janusgraph
    env_file:
      - janusgraph.env
    ports:
      - "8182:8182"

gruckion

#!/bin/sh

####################################################################
# Check for Homebrew, install if we don't have it
####################################################################

if test ! $(which brew); then
    echo "Installing homebrew..."
    ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
fi

ursulacj

Create a branch on Github using API and Python

Created as a module that can be imported or run. Requires built in JSON, requests, and datetime modules.

Allows you to clone a branch on Github using the Github Git Database API Endpoints.

Forked Gist from:

• auwsome/Create-branch-with-Github-API.md

See:

• http://stackoverflow.com/questions/9506181/github-api-create-branch

ankurk91

DNSmasq wildcard on Ubuntu 18/20

• Install dnsmasq

sudo apt install -y dnsmasq
sudo apt install -y resolvconf

• 💡 The dnsmasq service will fail to start, you can ignore those errors for time being
• Disable the default systemd-resolved service