Show the 61 terms
Docker
Container- An isolated process that has its own filesystem and network view but shares the host’s Linux kernel.
Image- A read‑only snapshot of a filesystem that contains everything needed to run an application.
Namespace- A Linux feature that gives a container its own separate view of system resources like processes and networking.
Cgroups- Linux controls that limit and account for the CPU, memory, and other resources used by a container.
Immutable image ID hash- A fixed identifier shown by docker inspect that proves you are using exactly the same image binary each time.
docker run- Command that creates a container from an image and starts it, optionally running a specific command inside.
docker images- Command that lists all image snapshots stored locally on your machine.
docker ps- Command that shows the containers currently existing (running or stopped) on the host.
docker rm- Command that deletes a container, freeing its resources and removing it from the list shown by docker ps.
docker inspect- Command that displays detailed metadata about an image or container, such as its ID hash.
Dockerfile- A plain‑text file that contains step‑by‑step instructions for building a Docker image.
docker-compose.yml- A YAML configuration file that defines multiple services, their images, and how they should be started together.
n8n
Workflow- A saved sequence of connected steps (nodes) that n8n runs automatically to move or transform data between apps.
Node- A single building block in a workflow — each node performs one action, such as sending an email, filtering data, or calling an API.
Trigger node- A special node that sits at the start of a workflow and decides when it runs — for example, on a schedule, when a form is submitted, or when another app sends a signal.
Action node- A node that does something in an external service — such as creating a row in Google Sheets, sending a Slack message, or reading an email.
Core node- A built-in utility node that handles data processing or flow control without connecting to an external service — examples include IF, Filter, Merge, and Code.
Connection- The arrow drawn between two nodes on the canvas that tells n8n to pass data from one node to the next when the workflow runs.
Canvas- The visual drag-and-drop workspace inside n8n where you build a workflow by placing and connecting nodes.
Execution- One complete run of a workflow — n8n records what happened at each node so you can inspect inputs, outputs, and any errors afterward.
Credentials- Securely stored login details (such as API keys or passwords) that let n8n connect to an external service on your behalf without exposing secrets inside the workflow.
Webhook- A URL that n8n creates for you so that an outside app can instantly start your workflow by sending data to that address.
Expression- A small piece of JavaScript written inside double curly braces ({{ }}) that lets you pull in data from a previous node or do a quick calculation instead of typing a fixed value.
Item- A single unit of data travelling through a workflow — for example, one email, one spreadsheet row, or one API result.
Schedule trigger- A trigger node that starts a workflow automatically at a set time or repeating interval, similar to a calendar alarm.
IF node- A core node that checks a condition and sends each data item down one of two paths — True or False — so different actions can happen depending on the data.
Sub-workflow- A separate workflow that another workflow calls like a reusable function, helping you keep complex automations organised and avoid repeating the same steps.
Error handling- A set of features in n8n — including dedicated error workflows and the Stop And Error node — that let you define what should happen if a node fails instead of silently stopping.
Data mapping- The act of telling a node where to find its input by dragging a field from a previous node's output onto the current node's input — no code required.
Sticky note- A text annotation you can place anywhere on the canvas to explain what part of a workflow does, without affecting how it runs.
Template- A pre-built workflow shared by the n8n community that you can import and adapt instead of building from scratch.
Manual execution- Running a workflow by clicking the Execute button yourself, used for testing before you switch the workflow on for automatic production runs.
AnythingLLM
@agent- A mention you type in a chat message in AnythingLLM to explicitly start an agent session, giving the conversation access to tools like web search or file reading.
mintplexlabs/anythingllm- The official Docker Hub image name for AnythingLLM, which you reference when running the app inside a container on your own machine or server.
/api/docs- A URL path you open in your browser on a running AnythingLLM instance to see its full interactive API reference, listing every endpoint you can call from code.
requests- A popular Python library that lets your code send HTTP requests (GET, POST, etc.) to web addresses, commonly used to call REST APIs like AnythingLLM's.
workspace- A named container that holds a set of uploaded documents and its own chat history, keeping different projects or topics separate.
@agent- A prefix you type in a workspace chat to turn it into an active agent that can take actions (e.g. summarise the newest file) rather than only answer.
docker run- The command used to pull and start the official mintplexlabs/anythingllm server image so you can self-host AnythingLLM.
Show Citations- A toggle under an answer that reveals which uploaded files it was drawn from, so you can verify each claim against the source.
LM Studio
lms- The command-line tool bundled with LM Studio that lets you start the server, download models, and manage everything from a terminal instead of the desktop app.
lms server start- Launches LM Studio's local API server so other programs on your computer (or network) can send it requests and get AI responses back.
lms server stop- Gracefully shuts down the running LM Studio API server, terminating any in-progress requests before stopping.
lms server status- Prints whether the LM Studio API server is currently running and which port it is listening on.
lms --version- Prints the installed version number of the lms command-line tool — the actual documented subcommand is lms version, but both forms report the current CLI version.
llmster- The headless (no desktop window) daemon version of LM Studio designed for servers or machines without a screen — it runs as a standalone background service and can still serve models over the API.
hermes setup- A setup command for the Hermes AI agent that guides you through configuring your model provider, including connecting it to a local LM Studio server.
hermes --tui- Starts Hermes in its text user interface (TUI) mode — a keyboard-driven chat panel that runs entirely inside your terminal with live streaming and modal overlays.
chmod +x start-local-llm.sh- A shell command that marks a script file as executable on Mac or Linux so you can run it directly; without this step the operating system refuses to run the script.
pip install openai- The Python package-manager command that downloads and installs the OpenAI Python library, which LM Studio also accepts because it speaks the same API format.
http://localhost:1234/v1- The full address of LM Studio's OpenAI-compatible API server on your own machine — localhost means 'this computer', 1234 is the default port number, and /v1 is the path prefix for the OpenAI-compatible endpoints.
localhost:1234- The host and port where LM Studio's server listens by default — shorthand for 'your own machine, port 1234'.
localhost- A special hostname that always means 'this computer' — using it ensures the connection never leaves your machine.
http://<your-ip>:1234/v1- The address other devices on your local network use to reach your LM Studio server — replace <your-ip> with your computer's actual network IP address (e.g. 192.168.1.5).
0.0.0.0- A special network address meaning 'listen on all network interfaces' — when LM Studio binds to this (via lms server start --bind 0.0.0.0), devices on your local Wi-Fi or wired network can connect to it, not just your own computer.
openai- The name of a Python library originally made for OpenAI's cloud API; LM Studio intentionally speaks the same format, so you can reuse this library to talk to your local models instead.
api_key- A configuration field where you provide a password or token to authenticate with an API; LM Studio does not require a real key by default, but the field must still be present (any placeholder string works).
base_url- A configuration field that tells a client library where the API server lives — for LM Studio you set this to your local server address instead of OpenAI's cloud address.
config.yaml- A plain-text configuration file written in YAML format — tools like Hermes read this file at startup to know which server URL, model, and preferences to use.
~/.hermes/config.yaml- The main configuration file for the Hermes tool, stored in a hidden folder in your home directory — you edit it to point Hermes at your local LM Studio server.
~/.hermes/.env- A hidden environment-variable file inside the Hermes config folder where you can store API keys and secrets separately from the main config file.