This tutorial is dated Oct 2021, if it's much further on than that this information might be out of date.
This is a guide on setting up a static HTTPS website on your raspberry pi using docker and nginx. The aim is to have this running on the raspberry pi and to be able to access it from a host computer on the same local network. You should already be able to ssh into your pi from your host computer and have raspberry pi OS set up.
Internet connection and DNS routing are broken from WSL2 instances, when some VPNs are active.
The root cause seems to be that WSL2 and the VPN use the same IP address block, and the VPN routing clobbers WSL2's network routing.
This problem is tracked in multiple microsoft/WSL issues including, but not limited to:
WSL 2 uses a Hyper-V Virtual Network adapter. Network connectivity works without any issue when a VPN is not in use. However when a Cisco AnyConnect VPN session is established Firewall Rules and Routes are added which breaks connectivity within the WSL 2 VM. This issue is tracked WSL/issues/4277
Below outline steps to automatically configure the Interface metric on VPN connect and update DNS settings (/etc/resolv.conf) on connect/disconnect.
| #!/bin/bash | |
| # Usage: | |
| # 1. Copy the script into a text editor and save it with no extension | |
| # 2. Make it executable like so: chmod +x path/to/script | |
| # 3. Run it from the Terminal in one of two ways: | |
| # * path/to/script ipa_path="path/to/ipa" archive_path="path/to/xcarchive" | |
| # * path/to/script ipa_path="path/to/ipa" toolchain_path="path/to/toolchain" |
If you're encountering ping github.com failing inside WSL with a Temporary failure in name resolution, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.
This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf.
DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.
To upgrade WSL, follow these steps,
| pacman | |
| ====== | |
| view logs: /var/log/pacman.log | |
| update system | |
| # pacman -Syu | |
| list installed packages | |
| # pacman -Q |
I had some fun pimping my development setup during my summer vacation 🏖 🏝 and
here's what I came up with. A script toggle-dark-mode that toggles dark mode for
not only Mac OS, but also Hyper, tmux and vim at once. I'm gonna be so
productive now.. 😁
*(I've customized Hyper term to remove dead space on top for maximized windows,
| require "string" | |
| function checkBluetoothResult(rc, stderr, stderr) | |
| if rc ~= 0 then | |
| print(string.format("Unexpected result executing `blueutil`: rc=%d stderr=%s stdout=%s", rc, stderr, stdout)) | |
| end | |
| end | |
| function bluetooth(power) | |
| print("Setting bluetooth to " .. power) |
This guide helps you setup a configuration like: mopidy -> icecast -> listner (bot) Where you can use mopidy to play from a wide selection of sources for example Spotify. At the moment I know of no Discord bots capable of controlling an mpd/mopidy server so the adding of playlists have to go through a webinterface or similar. In this guide I will focus on setting up Spotify. The full config files will also be in the gist.
