apk add nano
nano /etc/apk/repositories
Uncomment the line "http://sjc.edge.kernel.org/alpine/vX.XX/community" where X.XX is the current stable number
apk add nano
nano /etc/apk/repositories
Uncomment the line "http://sjc.edge.kernel.org/alpine/vX.XX/community" where X.XX is the current stable number
| # Tasks definition | |
| # Tasks represent code or programs to be executed with the required parameters | |
| # Usage rules: | |
| # 1. Variables MUST NOT be made of other variables. This should be handled within the service integration | |
| # Implementation rules: | |
| # 1. Tasks MUST call at least one service | |
| # 2. Tasks MUST produce a result | |
| # 3. Tasks result object has 3 sub-objects: | |
| # the result code(integer), the execution log artifact (URL), the pipeline artifacts (URL) |
| import AVFoundation | |
| import VideoToolbox | |
| class H264Coder { | |
| var session: VTCompressionSession? | |
| var onFrame: ((CMSampleBuffer) -> Void)? | |
| let outputCallback: VTCompressionOutputCallback = { refcon, sourceFrameRefCon, status, infoFlags, sampleBuffer in | |
| guard let refcon = refcon, |
Before we look at some common commands, I just want to note a few keyboard commands that are very helpful:
Up Arrow: Will show your last commandDown Arrow: Will show your next commandTab: Will auto-complete your commandCtrl + L: Will clear the screen| -- config values | |
| local config = { | |
| debug = true, | |
| distance = 20 -- distance to check | |
| } | |
| -- variables | |
| local lastTargetPlayer, lastDist = nil, 100 | |
| local function debugTxt(...) |
There are lots of guides explaining Mastodon and the broader fediverse, but they often go into way too much detail. So I've written this guide - it only talks about the basics you need to know to start using it, and you can then gradually learn the rest from other helpful fediverse users. Let's get started!
The fediverse is very different from Twitter, and that is by design. It's made for building close communities, not for building a "global town square" or as a megaphone for celebrities. That means many things will work differently from what you're used to. Give it some time, and ask around on the fediverse if you're not sure why something works how it does! People are usually happy to explain, as long as it's a genuine question. Some of the details are explained in this article, but it's not required reading.
The most important takeaway is the "
| """ | |
| The most atomic way to train and run inference for a GPT in pure, dependency-free Python. | |
| This file is the complete algorithm. | |
| Everything else is just efficiency. | |
| @karpathy | |
| """ | |
| import os # os.path.exists | |
| import math # math.log, math.exp |
| #!/usr/bin/env bash | |
| set -euo pipefail | |
| # ── Arguments ───────────────────────────────────────────────────────────────── | |
| usage() { | |
| echo "Usage: $0 <host> <compose-file> [remote-dir] [--tag <version>]" | |
| exit 1 | |
| } |