- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 72 characters or less
- Reference issues and pull requests liberally after the first line
- When only changing documentation, include
[ci skip]
in the commit title - Consider starting the commit message with an applicable emoji
Discover gists
#ifndef _FOGEFOGE_H_ | |
#define _FOGEFOGE_H_ | |
#define CIMA 'w' | |
#define BAIXO 's' | |
#define DIREITA 'd' | |
#define ESQUERDA 'a' | |
#define BOMBA 'b' | |
void move_pers(char comando); |
var accessToken = JSON.parse(gameslist_config.dataset.profileGameslist).webapi_token; | |
var anticheatAppids = [10, 20, 30, 40, 50, 60, 70, 80, 240, 300, 320, 360, 440, 500, 550, 570, 730, 1200, 1250, 2100, 2200, 2210, 2350, 2400, 2620, 2630, 2640, 3970, 4000, 4920, 6510, 7940, 7950, 9010, 9050, 9070, 9460, 10000, 10010, 10030, 10050, 10090, 10170, 10180, 11610, 13140, 13180, 13520, 13540, 15120, 17300, 17330, 17340, 17430, 17500, 17520, 17570, 17700, 17710, 18110, 19900, 21090, 21110, 21120, 21970, 24840, 24860, 24960, 29520, 32690, 32700, 32770, 33930, 35450, 35450, 39000, 42160, 42160, 42700, 44350, 45500, 47790, 47830, 48190, 49400, 55100, 55110, 58610, 61700, 61730, 63000, 63200, 63500, 63950, 65800, 70000, 72300, 90800, 91310, 102700, 102700, 104900, 107410, 109400, 200110, 201070, 201870, 202090, 202970, 202990, 203290, 203300, 204080, 204300, 208090, 208480, 209160, 209170, 209610, 209650, 209870, 211880, 212160, 212180, 212180, 212200, 212220, 212240, 212370, 212390, 212390, 212410, 212480, 212542, 2126 |
# | |
# INPUT - Logstash listens on port 8514 for these logs. | |
# | |
input { | |
udp { | |
port => "8514" | |
type => "syslog-cisco" | |
} | |
#lang racket | |
;; | |
;; These are some examples of different ways to compute factorials | |
;; using various paradigms and features provided by Racket. There | |
;; are more options available in packages which are not imported | |
;; by default, but that rabbit hole goes very deep indeed. | |
;; | |
;; Comments and suggestions welcome! | |
;; leo@lwh.jp |
As often happens, I found the official documentation and forum answers to be "close, but no cigar", and so had to experiment a little to get things working.
The main problem for me was a lack of concrete configuration examples. That's not entirely GitHub's fault: having migrated from Google Domains to Namecheap in the middle of this project, I was once again reminded of how many different ways there are to do things in the name service universe [1].
Although you'd think the simplest setup would be to merely configure for the subdomain case (https://www.example.com), in my experience using the apex domain (https://example.com) instead resulted in fewer complications.
So here's my recipe for using a custom domain with GitHub pages where Namecheap is the DNS provider:
Just a quick update before we dive in: what we're actually doing here is running Raspberry Pi OS (64-bit) on a QEMU virtual ARM setup. This isn't full-blown hardware emulation of the Raspberry Pi 4, but more about creating a virtual environment for the OS. It doesn't mimic all the specific hardware features of the Pi 4, but it's pretty useful and great for general testing. I turned to this solution mainly to extract a modified sysroot from the Raspberry Pi OS, something not readily available in other resources. For those looking into detailed emulation of the actual Raspberry Pi 4's hardware in QEMU, check out this link for the latest updates: https://gitlab.com/qemu-project/qemu/-/issues/1208.
Hope it helps! :D
Shortcomings: No GUI yet, only console.
#!/bin/bash | |
# This script helps provide project specific options to the dotnet ef cli. | |
if [ $# -eq 0 ]; then | |
echo "Usage: ./dotnet-ef.sh <command> [options]" | |
exit 1 | |
fi | |
args=( |