Terminal
Terminal/Skill
Answers JFrog Platform sizing, deployment pattern and disaster recovery questions, citing the official reference architecture pages.
By JFrog
Works with
npx skills add jfrog/jfrog-skills --skill jfrog-reference-architecturePlanning skill for topology, sizing, and deployment. Answers must come from live fetches of the JFrog Platform Reference Architecture — not from training data or duplicated tables in this repo.
../jfrog/SKILL.md for JFrog Platform concepts, product vocabulary, and routing to other workflows.jf CLI required for planning-only questions (no live instance needed).| Allowed in this skill | Not allowed |
|---|---|
| Fetch procedures, workflows, output templates | Sizing RPM tables, use-case narratives, deployment checklists copied from the site |
| Helm chart preference (jfrog-platform on Kubernetes) | Hardcoded slug lists or criteria |
Every factual claim (numbers, template names, limitations, infrastructure guidance) must come from a WebFetch in the current session. If fetch fails, retry or ask the user to open the URL — do not guess from memory.
Citations: Use the URL: line from the relevant section in the fetched content (public HTML URL). You may note content was read from llms-full.txt.
For fetch URLs, size thresholds, and the fallback ladder, see references/doc-access.md.
| Symptom | Mitigation |
|---|---|
| Sizing numbers or use-case names not on the official site | WebFetch ref-arch first; cite URL: from the fetch — not training data |
small template recommended for production | Re-read production warnings in the fetched Artifactory/Xray sizing sections |
| SaaS section missing or 404 | SaaS paths use prefix jfrog-saas, not saas |
| HA storage guidance wrong | Per ref arch: cluster-file-system or object storage — not file-system for HA |
WebFetch blocked, truncated, or over size limits | Request full_network; downgrade per references/doc-access.md |
Before answering a reference-architecture question:
WebFetch https://jfrog.com/reference-architecture/llms-full.txt (primary).references/doc-access.md (sitemap + targeted index.md).Request full_network (or the runtime equivalent) when WebFetch is blocked.
Sections are separated by --- and typically include:
# <Title>URL: https://jfrog.com/reference-architecture/...> <summary>Use only text from the fetch. For recommendations, cite the section’s URL: line.
| User intent | Where to look in llms-full | Fallback |
|---|---|---|
| Sizing | # Sizing, # AWS Sizing, Azure, GCP sections | .../self-managed/deployment/sizing/index.md |
| Topology / use case | Matching title + URL: for SaaS (jfrog-saas) or self-managed | That path’s index.md |
| List use cases | All URL: lines containing /use-cases/ | sitemap.xml |
| Deployment / install | Deployment and considerations sections | .../deployment/index.md |
| Disaster recovery | DR playbook / tiers sections | Matching index.md |
SaaS paths use prefix jfrog-saas, not saas.
llms-full.txt (unless downgraded to single-page fetch).AskQuestion when available; otherwise numbered options using labels from the fetched table only.small through 2xlarge) and cite the sizing page URL: from the dump.-f sizing/platform-<template>.yaml. WebFetch the chart README if the user wants exact install commands.## Recommended sizing
- **Template**: <from fetched table>
- **Artifactory**: <RPM and concurrent connections from fetched table>
- **Xray** (if applicable): <from fetched Xray table>
- **Source**: <URL: line from Sizing section>
- **Helm**: `helm upgrade --install` with `-f sizing/platform-<template>.yaml` on chart `jfrog/jfrog-platform`
- **Caveats**: <Notes / additional factors from fetched Sizing section>
llms-full.txt.URL: lines containing /use-cases/ from the dump; group under JFrog SaaS vs Self-managed. Fallback: sitemap.xml if the user wants sitemap-complete listing.URL:. If the dump is insufficient for one page, WebFetch https://jfrog.com/reference-architecture/<path>/index.md for that URL: path.llms-full.txt.cluster-file-system for HA, Enterprise license for replicaCount > 1.WebFetch the chart README when the user needs install snippets, OpenShift (openshift-values.yaml last), or RabbitMQ quorum files.## Deployment recommendation
- **Runtime**: Kubernetes + jfrog-platform Helm chart
- **Reference**: <URL: from deployment-related sections>
- **Key considerations**: <bullets from fetched considerations sections>
- **Helm** (if requested): <commands from chart README fetch>
Sizing: User asks what sizing to set for Artifactory → bootstrap llms-full → ask peak RPM using fetched table options → recommend template and Helm sizing file.
List use cases: User asks for all documented use cases → bootstrap llms-full → list grouped by SaaS vs self-managed from URL: lines in dump.
Topology: User needs DR across two regions → clarify SaaS vs self-managed → recommend active-passive (or related) section from dump with URL: citations.
Deploy: User wants Artifactory on EKS → deployment + AWS sizing sections from dump → jfrog-platform chart with external DB and sizing values file.