CentOS, Ubuntu, Slackware, etc. Whatever Linux-based OS it is, you can create a bootable USB for it by using a Mac.
Download it, copy it, whatever it takes to prepare that Linux-based OS .iso file
[initial]Web[/initial][column_1][font_small][red]This is text in column 1.\n [column_2]This is text in column 2.\n |
# This ESPHome configuration file is for a GeekMagic Display device (esp01). | |
# It sets up the device to display pages of text and notifications, | |
# with customizable intervals and padding. The display is updated | |
# periodically and can show different pages based on Home Assistant sensors. | |
# The configuration includes: | |
# - WiFi setup with fallback hotspot | |
# - Web server for remote access | |
# Usage: |
CentOS, Ubuntu, Slackware, etc. Whatever Linux-based OS it is, you can create a bootable USB for it by using a Mac.
Download it, copy it, whatever it takes to prepare that Linux-based OS .iso file
hs.loadSpoon('SpoonInstall') | |
spoon.SpoonInstall.use_syncinstall = true | |
Install = spoon.SpoonInstall | |
log = hs.logger.new('init', 5) | |
-- function debugUI(msg, table) | |
-- log:d(msg) | |
-- log:d(hs.inspect(table)) | |
-- end |
# | |
# udev rule | |
# Mount USB drive to the media directory using the partition name as mount point | |
# | |
# Description: | |
# Created for Home Assistant OS, this rule mounts any USB drives | |
# into the Hassio media directory (/mnt/data/supervisor/media). | |
# When a USB drive is connected to the board, the rule creates one directory | |
# per partition under the media directory. The newly created partition is named | |
# as the partition name. If the partition does not have a name, then the following |
# needs SSH active on ESXi host | |
# needs SSH public key from HomeAssistant in ESXi ssh authorized_keys config '/etc/ssh/keys-<username>/authorized_keys' Have a look here: https://kb.vmware.com/s/article/1002866 | |
# get VM ID on ESXi commandline by 'vim-cmd vmsvc/getallvms' You need to set this in the scripts commands where 00 is shown | |
# needs VMware Tools installed on the VM you want to control | |
# change in Switch: ESXi ip address, VM ID, switch name and switch friendly name | |
switch: | |
# https://www.home-assistant.io/integrations/switch.command_line/ | |
- platform: command_line |
# Set pixoo_post_address in your secrets.yaml to your Pixoo64 rest api post address | |
# pixoo_post_address: http://192.168.foo.bar/post | |
# if you host Pixoo-Rest you could set url in the pixoo_rest_imageurl command | |
sensor: | |
- platform: rest | |
name: pixoo64 Data | |
resource: !secret pixoo_post_address | |
method: POST | |
payload: '{ "Command" : "Channel/GetAllConf" }' | |
value_template: "OK" |
#!/bin/sh | |
prog_name=${0##*/} | |
version=1.0 | |
version_text="Boilerplate for new scripts v$version" | |
options="h o: q v V" | |
help_text="Usage: $prog_name [-o <text>] [-hqvV] [<file>]... | |
Boilerplate for new scripts |
One of my colleagues shared an article on writing (good) Git commit messages today: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
$ brew install fish | |
$ echo "/usr/local/bin/fish" | sudo tee -a /etc/shells | |
$ chsh -s `which fish` |