In this guide we will only focus on using the prebuilt images from Docker Hub.
Prerequisites: You have Git, Docker, Docker compose and Nginx pre-installed.
Clone Mastodon's repository.
#!python3 | |
# Based on: https://community.home-assistant.io/t/api-for-changing-entities/282114/3 | |
import asyncio | |
import json | |
import os | |
import re | |
import sys | |
import yaml # type: ignore | |
import websockets |
In this guide we will only focus on using the prebuilt images from Docker Hub.
Prerequisites: You have Git, Docker, Docker compose and Nginx pre-installed.
Clone Mastodon's repository.
APT::Default-Release "testing"; |
SYNOPSIS
Creates an M3U playlist for an HDHomerun tuner
DESCRIPTION
Downloads the lineup from an HDHR tuner, specified by IP address and transforms it into an M3U plalist
When you don't specify an output file, the m3u content will be printed out for preview.
#!/usr/bin/env bash | |
name=fooAlert-$RANDOM | |
url='http://localhost:9093/api/v1/alerts' | |
bold=$(tput bold) | |
normal=$(tput sgr0) | |
generate_post_data() { | |
cat <<EOF | |
[{ |
This Gist contains some scripts for Tinc, in order to configure the routing tables for a remote subnet on Windows (ie. if a remote system wants to expose an entire subnet over the VPN). Tinc does not configure the routing tables by default, which is why these scripts are needed. See the mailing list thread here: https://www.tinc-vpn.org/pipermail/tinc/2018-December/005340.html
Place the files in the Tinc network directory (eg. C:\Program Files\Tinc\netname\
) and change $interface
in functions.ps1
to match the name of the Tinc interface configured in tinc.conf
import sys | |
import extract_icon | |
import os | |
import argparse | |
class MorIcons: | |
""" | |
parses an ``APPS.INF`` file, dumps all icons from a PE binary and | |
generates an HTML file with all the icons and associated program | |
names |
Note:
When this guide is more complete, the plan is to move it into Prepack documentation.
For now I put it out as a gist to gather initial feedback.
If you're building JavaScript apps, you might already be familiar with some tools that compile JavaScript code to equivalent JavaScript code:
#!/bin/bash | |
name=$RANDOM | |
url='http://localhost:9093/api/v1/alerts' | |
echo "firing up alert $name" | |
# change url o | |
curl -XPOST $url -d "[{ | |
\"status\": \"firing\", |
So you’ve created a really neat console app, but it’s growing and you need a way to keep it all neatly organized and preferrably with some Good Practices.
The guys at Entity Framework have thought about this and structured their console app really neatly. Today, we’ll take the ninja app we built previously and make it all look pretty and stuff.