Duncan Lock dflock

58 bytes of CSS to look great nearly everywhere

When making this website, i wanted a simple, reasonable way to make it look good on most displays. Not counting any minimization techniques, the following 58 bytes worked well for me:

main {
  max-width: 38rem;
  padding: 2rem;
  margin: auto;
}

Last tested version: 5.7.20

0. Preparation

Make sure LXC has more than 12GB, otherwise Unifi fails to start!

1. Follow steps from Ubiquiti site

https://help.ubnt.com/hc/en-us/articles/220066768-UniFi-How-to-Install-Update-via-APT-on-Debian-or-Ubuntu

# for unifi
echo 'deb http://www.ubnt.com/downloads/unifi/debian stable ubiquiti' | sudo tee /etc/apt/sources.list.d/100-ubnt-unifi.list

Enable #enable-devtools-experiments flag in chrome://flags section.
Open Chorme Devtools and check Settings > Experiments > Allow extensions to load custom stylesheets.

Create the following four files in a dedicated folder.

3.1. devtools.html

<html>
<head></head>
<body><script src="devtools.js"></script></body>

Checking the State of Your States

If applicable, make sure your design component accounts for all these states. This is basically copied from the Nine States of Design Medium article. 😛

Initial state: What happens before your component does anything? Maybe it’s the first time a user sees it. Maybe it’s not activated yet. Essentially, the component exists but hasn’t started.
Loading state: Have you accounted for when a user will be waiting for something to happen? What does that look like?
Empty state: Your component has initialized, but it’s empty. No data. No Items. Now may be a good time to get the user to act (“Do this thing!”), or to reward them (“Good job, everything is taken care of”).
One state: You have some data. On an input, this may be after the first keystroke. In a list, it might be when you have one item (or one left).
Some data state: This is usually what you think

Extend Ambari

Introduction

Hortonworks wrote a great article how to add new components into Amabri:

https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=38571133

Unfortunately, this document is not enough if you really want to add your own component.

	# Instructions for installing Pi-hole 4.2 on UniFi CloudKey Gen 1 (UC-CK) running firmware 0.13.6
	# Pi-hole will need to be completely re-installed after every FW update or if CloudKey is reset to defaults.

	# Verify UC-CK is running firmware v0.13.6 (or later) before installing Pi-hole. If not, do:
	ubnt-systool fwupdate https://dl.ubnt.com/unifi/stage/cloudkey/firmware/UCK/UCK.mtk7623.v0.13.6.7ad551e.190225.0939.bin

	# UC-CK firmware v0.13.6 downgrades UniFi Controller to 5.10.17. Upgrade to 5.10.19 with:
	cd /tmp
	wget https://dl.ubnt.com/unifi/5.10.19/unifi_sysvinit_all.deb
	dpkg -i unifi_sysvinit_all.deb

	#!/bin/bash
	# =============================================================================
	# Author: Chu-Siang Lai / chusiang (at) drx.tw
	# Filename: teams-chat-post-for-workflows.sh
	# Modified: 2024-07-22 11:44 (UTC+08:00)
	# Description: Post a message to Microsoft Teams via "Post to a chat when a webhook request is received" workflows.
	# Reference:
	#
	# - https://gist.github.com/chusiang/895f6406fbf9285c58ad0a3ace13d025
	# - https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

	### sqlmd
	# Bash function for outputting SQLite results in Markdown-friendly table

	### Dependency:
	# csvlook can be found here: http://csvkit.readthedocs.io/en/540/scripts/csvlook.html

	### USAGE
	# $ sqlmd "SELECT name, age FROM people;" optional_db_name_argument.sqlite

	### OUTPUT

	#! /bin/bash
	# Usage:
	# ./git-move.sh path/to/file/or/dir path/to/destination/repo
	echo "creating patch for path ${1}"
	git log --name-only --pretty="format:" --follow "${1}" \
	\| sort -u \| \
	xargs git log --pretty=email --patch-with-stat --reverse --full-index --binary -m --first-parent -- > "${2}/_patch_" \
	&& echo "moving to destination repo at ${2}" \
	&& cd "${2}" \
	&& echo "applying patch" \

	#!/bin/bash
	#
	# git get
	#
	# Place this script in your path, so that git(1) can find it. Presto!
	# You can now type `git get` instead of `git pull` and enjoy the
	# advantages of rebasing atop instead of merging remote changes.
	#
	# If you have local changes, use `git get --stash` to stash and
	# pop afterwards your changes automatically.