Mang Ngân Trúc omnicortex

dynapt — Experimental setup tutorial

Introduction

Welcome to the experimental setup tutorial for dynapt, the dynamic APT repository.

If you're reading this, you might be frustrated that an app you're using doesn't offer automated updates, by way of an APT repository, a PPA, or a Flatpak.

LOCATION=$(curl -s https://api.github.com/repos/<YOUR ORGANIZTION>/<YOUR REPO>/releases/latest \
| grep "zipball_url" \
| awk '{ print $2 }' \
| sed 's/,$//'       \
| sed 's/"//g' )     \
; curl -L -o <OUTPUT FILE NAME> $LOCATION

for example:

Experimental Docker Libnetwork DHCP Driver

The DHCP driver is intended for users to be able to integrate Docker IP address management with their existing IPAM strategies that use DHCP for dynamic address assignment. DHCP enables users to allocate addresses in an organized fashion that will prevent overlapping IP address assignment by associating a unique MAC address from the container eth0 Ethernet interface to an IP address as determined by the DHCP pools defined in the DHCP configuration.

This driver only provides the DHCP client functionality. It does not include a DHCP server. The default driver offers single-host IPAM or for distributed multi-host orchestrated IPAM see the libnetwork overlay driver.

Getting Started

Download the driver compiled into Docker Engine - docker binary with libnetwork test dhcp client spam driver

	services:
	forgejo:
	image: codeberg.org/forgejo/forgejo:1.19.3-0
	tmpfs: ["/data"]
	stop_signal: SIGKILL
	ports: [ "3000:3000", "8000:8000" ]
	environment:
	# @see https://docs.gitea.com/next/administration/config-cheat-sheet

	GITEA__database__DB_TYPE: sqlite3

	$HOSTALIASES no longer works with glibc (https://bugs.launchpad.net/debian/+source/glibc/+bug/1483187)

	For my project, I needed to create a user specifc hosts file.

	First clone this repo - https://github.com/figiel/hosts.git

	################ README #####################################

	hosts - wrapper for libc which provides defining host aliases in a per-user file

	set -e

	set -u

	# hat-tips:
	# - http://codeghar.wordpress.com/2011/12/14/automated-customized-debian-installation-using-preseed/
	# - the gist

	# required packages (apt-get install)
	# xorriso

	import bs4.dammit
	import bs4.builder._htmlparser
	from bs4 import BeautifulSoup

	# when analyzing spam, we always run into situations where the sender tries
	# hard to obfuscate their input in order to sneak by spam detecting engines.
	# instead of "ABC", they'll use HTML Entity references; ABC in
	# order to extract the viewer readable segments, we need a parser. most
	# parsers try to be smart and clean things up. BeautifulSoup and lxml are
	# two common parsers. lxml is largely compiled C so we can't tweak it very

	Create Dummy ALSA Devices (en mass)
	Written by Mike C. Fletcher on April 16, 2012 in Tuxedo.

	Since this was a bit of a pain to track down, here's the process, on an Ubuntu Server 12.04 machine, to create many ALSA dummy devices:

	$ cat /etc/modprobe.d/alsa-dummy.conf
	options snd-dummy enable=1,1,1,1,1,1,1,1,1,1,1,1 pcm_devs=4,4,4,4,4,4,4,4,4,4,4,4 fake_buffer=0,0,0,0,0,0,0,0,0,0,0,0
	$ modprobe snd-dummy
	That sample creates 48 dummy devices (on 12 cards), though that's likely more than you'll ever need. The fake_buffer array means they should all have a real internal buffer. The "enable" array is specifying how many cards to create. The pcm_devs array specifies how many pcm devices to have on each card.