| require "digest" | |
| require "rack" | |
| # This class encapsulates a unit of work done for a particular tenant, connected to that tenant's database. | |
| # ActiveRecord makes it _very_ hard to do in a simple manner and clever stuff is required, but it is knowable. | |
| # | |
| # What this class provides is a "misuse" of the database "roles" of ActiveRecord to have a role per tenant. | |
| # If all the tenants are predefined, it can be done roughly so: | |
| # | |
| # ActiveRecord::Base.legacy_connection_handling = false if ActiveRecord::Base.respond_to?(:legacy_connection_handling) |
| #!/bin/bash | |
| # ───────────────────────────────────────────────────────────────────────────── | |
| # Production Docker Host Setup & Hardening Script — v3.1.0 | |
| # For Ubuntu Server 24.04 LTS (Noble) and 26.04 LTS (Resolute) | |
| # Suitable for both Kamal 2.x deployment hosts and remote builder hosts | |
| # | |
| # Part of RailsFast (https://railsfast.com) — free & open source, MIT licensed. | |
| # | |
| # Usage (as root, on a fresh server): |
| #!/usr/bin/env ruby | |
| # Place in your project (don't forget to chmod +x): | |
| # bin/autoload-check | |
| # Allow these files to be fixed later | |
| allowlist = [ | |
| "ExampleClass" # why? | |
| ] |
For years, people have been using jemalloc with ruby. There were various benchmarks and discussions. Legend had it that Jemalloc 5 didn't work as well as Jemalloc 3.
Then, one day, hope appeared on the horizon. @wjordan offered a config for Jemalloc 5.
FROM ruby:3.1.2-bullseye
RUN apt-get update ; \
| import boto3 | |
| ec2_client = boto3.client('ec2') | |
| rds_client = boto3.client('rds') | |
| rdsNetworkInterfaces = ec2_client.describe_network_interfaces( | |
| Filters=[ | |
| { | |
| 'Name': 'attachment.instance-owner-id', | |
| 'Values': [ |
The official guide for setting up Kubernetes using kubeadm works well for clusters of one architecture. But, the main problem that crops up is the kube-proxy image defaults to the architecture of the master node (where kubeadm was run in the first place).
This causes issues when arm nodes join the cluster, as they will try to execute the amd64 version of kube-proxy, and will fail.
It turns out that the pod running kube-proxy is configured using a DaemonSet. With a small edit to the configuration, it's possible to create multiple DaemonSets—one for each architecture.
Follow the instructions at https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ for setting up the master node. I've been using Weave Net as the network plugin; it see
My Elasticsearch cheatsheet with example usage via rest api (still a work-in-progress)
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
