Dimitri dpilarsk

Beast Mode

Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.

Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1

Installation Instructions

Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
Select "Create new custom chat mode file"

Simply include the file within your configuration.yaml file like this:

# ...
input_number: !include input_numbers.yaml
# ...

Restart your Home Assistant to update the values (reloading YAML will not be enough).

Longhorn best practices

The following settings are provided as an example how longhorn should be configured in a production cluster, especially if it is deployed on Hetzner Cloud infrastructure.

Hetzner server nodes provide local storage and allow up to five attached volumes (with a size of up to 10TiB each) Local storage is provided by NVMe storage and therefore is much faster than the attached volumes, but limited in size (max 300GiB usable).

It is assumed that the cluster creation is already done, e.g. via terraform scripts provided by the great kube-hetzner project.

Initial configuration

Idiomatic Data Fetching using React Hooks

This post has been written in collaboration with @klervicn

Virtually all web apps and websites need to pull data from a server, usually through a JSON-returning API. When it comes to integrating data fetching in React component, the "impedence mismatch" between the React components, which are declarative and synchronous, and the HTTP requests, which are imperative and asynchronous, is often problematic.

Many apps use third-party libraries such as Redux or Apollo Client to abstract it away. This requires extra dependencies, and couple your app with a specific library to perform data fetching. In most cases, what we want is a direct way to integrate plain HTTP requests (e.g. using native fetch) for usage in React components.

Here we will discuss how we can use React Hooks to do this in an elegant, scalable manner.

Set GOPRIVATE to match your github organization

I keep fixing this up, but if it fails for you, check if these are better maintained https://tip.golang.org/cmd/go/#hdr-Configuration_for_downloading_non_public_code and https://golang.org/ref/mod#private-modules.

Cloning the repo using one of the below techniques should work correctly but you may still be getting an unrecognized import error.

As it stands for Go v1.13, I found in the doc that we should use the GOPRIVATE variable like so:

GOPRIVATE=github.com/ORGANISATION_OR_USER_NAME go get -u -f github.com/ORGANISATION_OR_USER_NAME/REPO_NAME

The 'go env -w' command (see 'go help env') can be used to set these variables for future go command invocations.

	---
	id: yggapi
	name: YggAPI
	description: Indexeur non-officiel pour YggTorrent (YGG) - MOVIES / TV
	language: fr-FR
	type: private
	encoding: UTF-8
	testlinktorrent: false
	links:
	- https://yggapi.eu/

	# Debian 10
	apt-get -y update
	apt-get -y upgrade --without-new-pkgs
	apt-get -y full-upgrade

	cat > /etc/apt/sources.list <<"EOF"
	deb http://deb.debian.org/debian/ bullseye main
	deb-src http://deb.debian.org/debian/ bullseye main
	deb http://security.debian.org/bullseye-security bullseye-security/updates main
	deb-src http://security.debian.org/bullseye-security bullseye-security/updates main

	brew install caddy mkcert nss dnsmasq

	mkcert -install

	mkcert '.app.test' '.cdn.test'

	# rename the certs and move them under /usr/local/etc/caddy/certs

	cat <<EOF > /usr/local/etc/caddy/Caddyfile
	.app.test:443, .cdn.test:443 {

	version: '3'
	services:
	app:
	image: nginx:alpine
	ports: ["80:80"]
	restart: unless-stopped

	restarter:
	image: docker:cli
	volumes: ["/var/run/docker.sock:/var/run/docker.sock"]

	DOMAIN_NAME=yourdomain.tld

	TZ=Europe/London