Skip to content

docs: Update Explore page references to Pod Templates section #384

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: Update Explore page references to Pod Templates section #384

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pods/templates/manage-templates.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ When creating a template, you'll configure several key components:
- A public registry like Docker Hub (e.g., `ubuntu:latest`, `pytorch/pytorch:latest`).
- Your own private registry (requires registry credentials).

**Template visibility:** Choose whether your template is available to others. Public templates are available to all Runpod users in the Explore section of the console, while private template are only accessible to you or your team members.
**Template visibility:** Choose whether your template is available to others. Public templates are available to all Runpod users in the Pod Templates section of the console, while private template are only accessible to you or your team members.

**Compute type:** Templates are restricted to specific compute types and can only be used with matching hardware:
- **NVIDIA GPU:** For GPU-accelerated workloads requiring CUDA support
Expand Down
2 changes: 1 addition & 1 deletion pods/templates/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ You can create custom templates for your own specialized workloads. These can be

You can discover and use existing templates through the Runpod console:

**Browse all templates:** Visit the **[Explore](https://www.console.runpod.io/explore)** section to find official templates maintained by Runpod and community templates created by other users.
**Browse all templates:** Visit the **[Pod Templates](https://console.runpod.io/hub?tabSelected=templates)** section to find official templates maintained by Runpod and community templates created by other users.

**Manage your templates:** Access templates you've created or that are shared within your team in the **[My Templates](https://www.console.runpod.io/user/templates)** section.

Expand Down
4 changes: 2 additions & 2 deletions tutorials/pods/comfyui.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,10 +41,10 @@ First, you'll deploy a Pod using a template that pre-installs ComfyUI and the Co

<Steps>
<Step title="Deploy a Pod from the ComfyUI template">
Go to the [Better Comfy Slim](https://console.runpod.io/explore/cndsag8ob0) template in the Runpod console and click **Deploy**.
Go to the [Pod Templates section](https://console.runpod.io/hub?tabSelected=templates) in the Runpod console, search for "Better Comfy Slim", and click **Deploy**.

<Note>
There are several ComfyUI templates available in the Runpod console, many with pre-installed models. We're using this one because it's extremely lightweight, but it comes with the ComfyUI Manager plugin pre-installed so you can easily install the specific models/nodes you need after deployment.
There are several ComfyUI templates available in the Runpod console, many with pre-installed models. We're using the Better Comfy Slim template because it's extremely lightweight, but it comes with the ComfyUI Manager plugin pre-installed so you can easily install the specific models/nodes you need after deployment.
</Note>
</Step>

Expand Down