This guide is for building your own Arch Linux ARM VM image and runnig in QEMU, UTM, Parallels...
1. qemu-img
2. fdisk
3. kpartx
4. bsdtar
const WORDLIST = ["abandon","ability","able","about","above","absent","absorb","abstract","absurd","abuse", | |
"access","accident","account","accuse","achieve","acid","acoustic","acquire","across","act", | |
"action","actor","actress","actual","adapt","add","addict","address","adjust","admit", | |
"adult","advance","advice","aerobic","affair","afford","afraid","again","age","agent", | |
"agree","ahead","aim","air","airport","aisle","alarm","album","alcohol","alert", | |
"alien","all","alley","allow","almost","alone","alpha","already","also","alter", | |
"always","amateur","amazing","among","amount","amused","analyst","anchor","ancient","anger", | |
"angle","angry","animal","ankle","announce","annual","another","answer","antenna","antique", | |
"anxiety","any","apart","apology","appear","apple","approve","april","arch","arctic", | |
"area","arena","argue","arm","armed","armor","army","around","arrange","arrest", |
Filter | Description | Example |
---|---|---|
allintext | Searches for occurrences of all the keywords given. | allintext:"keyword" |
intext | Searches for the occurrences of keywords all at once or one at a time. | intext:"keyword" |
inurl | Searches for a URL matching one of the keywords. | inurl:"keyword" |
allinurl | Searches for a URL matching all the keywords in the query. | allinurl:"keyword" |
intitle | Searches for occurrences of keywords in title all or one. | intitle:"keyword" |
Apologies for the snarky title, but there has been a huge amount of discussion around so called "Prompt Engineering" these past few months on all kinds of platforms. Much of it is coming from individuals who are peddling around an awful lot of "Prompting" and very little "Engineering".
Most of these discussions are little more than users finding that writing more creative and complicated prompts can help them solve a task that a more simple prompt was unable to help with. I claim this is not Prompt Engineering. This is not to say that crafting good prompts is not a difficult task, but it does not involve doing any kind of sophisticated modifications to general "template" of a prompt.
Others, who I think do deserve to call themselves "Prompt Engineers" (and an awful lot more than that), have been writing about and utilizing the rich new eco-system
Sequential prompt chaining in one method with context and output back-referencing.
main.py
- start here - full example using MinimalChainable
from chain.py
to build a sequential prompt chianchain.py
- contains zero library minimal prompt chain classchain_test.py
- tests for chain.py
, you can ignore thisrequirements.py
- python requirementsimport { Dispatch, SetStateAction, useState, useEffect, useCallback, useRef } from 'react'; | |
export type StorageArea = 'sync' | 'local'; | |
// custom hook to set chrome local/sync storage | |
// should also set a listener on this specific key | |
type SetValue<T> = Dispatch<SetStateAction<T>>; | |
/** |
version: '3' | |
services: | |
##### GitLab Stack ##### | |
##### GitLab Stack ##### | |
gitlab: | |
image: 'gitlab/gitlab-ce:latest' | |
restart: always | |
container_name: gitlab | |
hostname: # YOUR HOSTNAME ex. git.example.com |
# Clone llama.cpp | |
git clone https://github.com/ggerganov/llama.cpp.git | |
cd llama.cpp | |
# Build it | |
LLAMA_METAL=1 make | |
# Download model | |
export MODEL=llama-2-13b-chat.ggmlv3.q4_0.bin | |
wget "https://huggingface.co/TheBloke/Llama-2-13B-chat-GGML/resolve/main/${MODEL}" |
# Source: https://gist.github.com/vfarcic/78c1d2a87baf31512b87a2254194b11c | |
############################################################### | |
# How To Create A Complete Internal Developer Platform (IDP)? # | |
# https://youtu.be/Rg98GoEHBd4 # | |
############################################################### | |
# Additional Info: | |
# - DevOps MUST Build Internal Developer Platform (IDP): https://youtu.be/j5i00z3QXyU | |
# - How To Create A "Proper" CLI With Shell And Charm Gum: https://youtu.be/U8zCHA-9VLA |
Magic words:
psql -U postgres
Some interesting flags (to see all, use -h
or --help
depending on your psql version):
-E
: will describe the underlaying queries of the \
commands (cool for learning!)-l
: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)