Crosstyan crosstyan

Variables in the Caddyfile

Caddy is a super webserver that has many useful features. Caddy can enable very very powerful scenarios and many of them are documented in this Wiki. As these scenarios become more elaborate (some might say complex!) writing a caddy config file starts to feel more like programming than basic configuration.

When that starts to happen I find myself reaching out for variables to enable multiple scenarios in a single configuration file by manipulating those variables.

For those situations caddy has a few types of variables to consider. What I hope to do here is illuminate how to use these variable types in the Caddyfile.

A note about examples

I will use examples to illustrate the concepts. I use the respond directive to verify how caddy works.

Guide to build OpenCV from source with GPU support (CUDA and cuDNN)

Feb 22nd, 2022

System specification

Operating system: Ubuntu 20.04 x84_64 (64-bit)
Architecture: amd64
GPU: NVIDIA GeForce RTX 3090
Python 3.8

Install dependencies and recommeneded packages

This is a brief guide on how to install Archlinux as a WSL2 distribution and how to set up CUDA afterwards.

As of late, Window's WSL2 offers GPU passthrough from WSL2/Linux to Windows for NVidia graphics cards which allows to run (and develop) CUDA-based applications on the WSL2/Linux-side with almost native performance. Unfortunately, the official guides for the CUDA setup for WSL2/Linux are predominantly Ubuntu-specific. Here's to you, Arch!

1. Install Archlinux

Make sure that your Windows meets the dependencies and that your WSL2 is set up. See these instructions.

Archlinux is not among the default distributions available for WSL2. We'll install it from a tarball instead, a functionality offered natively by the WSL.

The Windows version of OpenSSH client doesn't include a ssh-copy-id command. I don't know why. If it does one day, then this gist can be ignored.

This script is written in PowerShell as the legacy program cmd.exe is not flexible enough for the required options.
Download the file ssh-copy-id.ps1 to your Windows PC, or copy and paste its contents to a file of the same name.
Run the script passing your linux account ssh information (for example powershell .\ssh-copy-id.ps1 pi@raspberrypi.local). If you use a non-standard port add the parameter -port=nnnn. This should work with any Linux platform.
Run the command for each linux account you connect with. You will be prompted for your Linux host password. If you have more than 1 account on any machine, you must do this for each account.

If the script won't run, then run this command once

Set-ExecutionPolicy RemoteSigned CurrentUser

Source: https://wiki.archlinux.org/title/Visual_Studio_Code#Blurry_text_under_Wayland

Due to Electron issues Visual Studio Code defaults to run under XWayland which may cause blurry text if you're using HiDPI screens.

In order to fix this issue you need to force Electron to run under Wayland by adding --enable-features=UseOzonePlatform --ozone-platform=wayland, for example you'll be launching VSCode like

$ code --enable-features=UseOzonePlatform --ozone-platform=wayland

This fix can be made permanent by creating a .desktop file or by directly editing /usr/share/applications/visual-studio-code.desktop

Dynamic Penetration Guide (EN) (日本語版)

for Dynamic Penetration System v1_21 (Gumroad)
I noticed some things aren't super clear for the Dynamic Penetration System, there is a lack of documentation to some extent.
This Guide does not describe how to set up penetrators using the provided script, but rather aids people in the manual process. Instructions for the Script may come at a later point.

Channels:

Light Ranges correspond to channels.

let's say you have a C++ project in Nix that you want to work on with CLion so that the nix dependencies are available.

create a .nix utility directory in your project directory.
put the below nix-run.sh and nix-cmake.sh in the .nix directory.
in the .nix directory create symlinks for make, gcc, g++ - and maybe more tools, that need to have the nix dependencies and build tools available - and point them to nix-run.sh
then, in Settings -> Build, Execution, Deployment -> Toolchains set CMake to the path to nix-cmake.sh and point all other build tools to the symlinks you've created.

Collecting the trace

Windows has the tools needed to collect traces for the bluetooth stack built-in, they just need to be configured. There are step by step instructions and scripts at Microsoft/busiotools, but I have copied some of the relevant details below.

To start the trace, create a temporary directory, then run this from an admin PowerShell prompt:

wget https://github.com/Microsoft/busiotools/raw/master/bluetooth/tracing/BluetoothStack.wprp -outfile .\BluetoothStack.wprp

	/*
	* This document is provided to the public domain under the
	* terms of the WTFPL license.
	*/

	This is

	This is a combination of
	- [How to boot Arch Linux ARM in QEMU (patched for M1)](https://gist.github.com/thalamus/561d028ff5b66310fac1224f3d023c12) - thanks to Avatar
	Will Tisdale

	const std = @import("std");
	const expect = std.testing.expect;

	fn Functor(
	comptime F: fn (comptime type) type,
	) type {
	return struct {
	fmap: fmap_type,

	const Self = @This();