Skip to content

Commit

Permalink
fix(docs): add correct registry to Docker image tags
Browse files Browse the repository at this point in the history
  • Loading branch information
maxnatamo authored Sep 8, 2024
1 parent f723f63 commit 0e7280e
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/docs/getting-started/installation.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Lists all the available options for installing/building Fetcharr. Some of these

:::warning

**Fetcharr is still early in development.** If you would like to help test the bleeding edge, please use the image `fetcharr/fetcharr:develop`!
**Fetcharr is still early in development.** If you would like to help test the bleeding edge, please use the image `ghcr.io/fetcharr/fetcharr:develop`!

:::

Expand All @@ -34,7 +34,7 @@ Be sure to replace `/path/to/appdata/config` with a valid host directory path. I
-e TZ=Europe/Copenhagen \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
fetcharr/fetcharr:latest
ghcr.io/fetcharr/fetcharr:latest
```
</TabItem>
<TabItem value="docker-compose" label="Docker Compose">
Expand All @@ -43,7 +43,7 @@ Be sure to replace `/path/to/appdata/config` with a valid host directory path. I
```yaml title="compose.yaml"
services:
fetcharr:
image: fetcharr/fetcharr:latest
image: ghcr.io/fetcharr/fetcharr:latest
container_name: fetcharr
environment:
- TZ=Europe/Copenhagen
Expand Down Expand Up @@ -84,4 +84,4 @@ Afterwards, build the Docker image using [NUKE](https://nuke.build):

You don't need to have NUKE installed for `build.cmd` to work.

:::
:::

0 comments on commit 0e7280e

Please sign in to comment.