This was tested on a FRESH Raspbian Bookworm Lite installation. Proceed with caution.
EDIT 23/12/2023: Removed dead download link and added own release
EDIT 09/06/2024: Force wayland after install
EDIT 06/07/2024: Add Troubleshooting section
EDIT 11/09/2024: Rearrange config file
| """ | |
| Implementation of the Selenium Chrome WebDriver | |
| with HTTP Response data included via the ChromeDriver performance logging capability | |
| https://sites.google.com/a/chromium.org/chromedriver/logging/performance-log | |
| The ChromeWebDriver response attribute(s) contain a dict with information about the response | |
| { | |
| "connectionId": [Integer], | |
| "connectionReused": [Boolean], | |
| "encodedDataLength": [Integer], |
Get the latest raspbian image here
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
| version: '2' | |
| services: | |
| nginx: | |
| image: jwilder/nginx-proxy | |
| container_name: nginx-proxy | |
| environment: | |
| - DEFAULT_HOST=nuget.hangfire.io | |
| links: | |
| - proget | |
| ports: |
| """ | |
| Copyright 2019 Jason Hu <awaregit at gmail.com> | |
| Licensed under the Apache License, Version 2.0 (the "License"); | |
| you may not use this file except in compliance with the License. | |
| You may obtain a copy of the License at | |
| http://www.apache.org/licenses/LICENSE-2.0 | |
| Unless required by applicable law or agreed to in writing, software |
| /** | |
| * Code to run a basic automatic greenhouse. | |
| * | |
| * - Temp/humidity sensor | |
| * - Soil moisture sensor | |
| * - Water pump | |
| * - Ventilation fan | |
| * | |
| * @see http://saettfro.com/vaxthus/ | |
| */ |
| /* | |
| * Hydroponics system monitor | |
| * J. Devine | |
| * Runs on Arduino Pro 5V | |
| * Sensors: | |
| * DFRobot pHmeter V1.1 | |
| * Waterproof DS18B20 water temperature sensor | |
| * TMP36 air temperature sensor | |
| * HC-SR04 distance sensor (for water level..) | |
| * A european two pin plug for EC measurements |
| """ | |
| http://stackoverflow.com/questions/28022432/receiving-rtp-packets-after-rtsp-setup | |
| A demo python code that .. | |
| 1) Connects to an IP cam with RTSP | |
| 2) Draws RTP/NAL/H264 packets from the camera | |
| 3) Writes them to a file that can be read with any stock video player (say, mplayer, vlc & other ffmpeg based video-players) | |
| Done for educative/demonstrative purposes, not for efficiency..! |
Note: These are rough notes and there may be some variance as versions of raspbian get updated but should be pretty reliable as a guide.
This gist provides some instructions and config in order to have your Raspberry PI automatically connect to a roamed network, however if it fails to discover an available network it will set itself up as a wireless access point for you to connect to.