Skip to content

Commit a102ec4

Browse files
committed
Change docker image to ghcr.io/imgproxy/imgproxy
1 parent 7d15484 commit a102ec4

47 files changed

Lines changed: 106 additions & 106 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313
<a href="https://imgproxy.net/blog/">Blog</a> |
1414
<a href="https://docs.imgproxy.net">Documentation</a> |
1515
<a href="https://imgproxy.net/#pro">imgproxy Pro</a> |
16-
<a href="https://hub.docker.com/r/darthsim/imgproxy/">Docker</a> |
16+
<a href="https://github.com/imgproxy/imgproxy/pkgs/container/imgproxy">Docker</a> |
1717
<a href="https://twitter.com/imgproxy_net">Twitter</a> |
1818
<a href="https://discord.gg/5GgpXgtC9u">Discord</a>
1919
</h4>

docs/configuration/loading_environment_variables.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ You can specify an AWS Access Key ID and a Secret Access Key by setting the stan
5050
AWS_ACCESS_KEY_ID=my_access_key AWS_SECRET_ACCESS_KEY=my_secret_key imgproxy
5151

5252
# same for Docker
53-
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it darthsim/imgproxy
53+
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it ghcr.io/imgproxy/imgproxy
5454
```
5555

5656
#### Shared credentials file
@@ -108,7 +108,7 @@ You can specify an AWS Access Key ID and a Secret Access Key by setting the stan
108108
AWS_ACCESS_KEY_ID=my_access_key AWS_SECRET_ACCESS_KEY=my_secret_key imgproxy
109109

110110
# same for Docker
111-
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it darthsim/imgproxy
111+
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it ghcr.io/imgproxy/imgproxy
112112
```
113113

114114
#### Shared credentials file

docs/getting_started.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@ This guide will show you how to quickly resize your first image using imgproxy.
1111
Let's assume you already have Docker installed on your machine — you can pull an official imgproxy Docker image, and you’re done!
1212

1313
```bash
14-
docker pull darthsim/imgproxy:latest
15-
docker run -p 8080:8080 -it darthsim/imgproxy
14+
docker pull ghcr.io/imgproxy/imgproxy:latest
15+
docker run -p 8080:8080 -it ghcr.io/imgproxy/imgproxy:latest
1616
```
1717

1818
If you don't have docker or if you want to deploy imgproxy to a cloud, you can check out our [installation guide](./installation.mdx) for more installation options.

docs/image_sources/amazon_s3.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ You can specify an AWS Access Key ID and a Secret Access Key by setting the stan
4242
AWS_ACCESS_KEY_ID=my_access_key AWS_SECRET_ACCESS_KEY=my_secret_key imgproxy
4343

4444
# same for Docker
45-
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it darthsim/imgproxy
45+
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it ghcr.io/imgproxy/imgproxy
4646
```
4747

4848
#### Shared credentials file

docs/installation.mdx

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,11 @@ There are multiple ways you can install imgproxy:
88

99
## Docker
1010

11-
imgproxy can (and this is highly recommended) be used as a standalone application inside a Docker container. Just pull the official image from Docker Hub:
11+
imgproxy can (and this is highly recommended) be used as a standalone application inside a Docker container. Just pull the official image from GitHub Container Registry:
1212

1313
```bash
14-
docker pull darthsim/imgproxy:latest
15-
docker run -p 8080:8080 -it darthsim/imgproxy
14+
docker pull ghcr.io/imgproxy/imgproxy:latest
15+
docker run -p 8080:8080 -it ghcr.io/imgproxy/imgproxy:latest
1616
```
1717

1818
You can also build your own image. imgproxy is ready to be dockerized out of the box:
@@ -62,8 +62,8 @@ heroku create your-application
6262
heroku stack:set container -a your-application
6363
heroku container:login
6464
# Replace "v3" with the imgproxy version you want to deploy
65-
docker pull darthsim/imgproxy:v3-amd64
66-
docker tag darthsim/imgproxy:v3-amd64 registry.heroku.com/your-application/web
65+
docker pull ghcr.io/imgproxy/imgproxy:v3-amd64
66+
docker tag ghcr.io/imgproxy/imgproxy:v3-amd64 registry.heroku.com/your-application/web
6767
docker push registry.heroku.com/your-application/web
6868
heroku container:release web -a your-application
6969
```
@@ -95,11 +95,11 @@ imgproxy can be deployed to [Dome](https://trydome.io/) with the click of a butt
9595
We don't provide packages for imgproxy yet, but you can use the `imgproxy-build-package` script to export a DEB, RPM, or TAR package from a Docker image:
9696

9797
```bash
98-
docker run -u0 --rm -it -v $(pwd):/dist darthsim/imgproxy:latest-amd64 imgproxy-build-package deb /dist
98+
docker run -u0 --rm -it -v $(pwd):/dist ghcr.io/imgproxy/imgproxy:latest-amd64 imgproxy-build-package deb /dist
9999
```
100100

101101
Where:
102-
* `darthsim/imgproxy:latest-amd64` is the imgproxy Docker image you want to export the package from. Take note that we used the `-amd64` suffix in the image tag. This suffix ensures that the image built for the `AMD64` CPU architecture will be used. If you're using an `ARM64` CPU, you should replace the `-amd64` suffix with `-arm64`.
102+
* `ghcr.io/imgproxy/imgproxy:latest-amd64` is the imgproxy Docker image you want to export the package from. Take note that we used the `-amd64` suffix in the image tag. This suffix ensures that the image built for the `AMD64` CPU architecture will be used. If you're using an `ARM64` CPU, you should replace the `-amd64` suffix with `-arm64`.
103103
* `$(pwd)` is the directory on your host machine where the package will be saved. `$(pwd)` is a shell command that returns the current working directory. You can replace it with the path to the directory where you want to save the package.
104104
* `deb` is the package format you want to export. You can replace it with `rpm` or `tar` to export an RPM or TAR package.
105105

docs/monitoring/cloud_watch.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ You can specify an AWS Access Key ID and a Secret Access Key by setting the stan
4343
AWS_ACCESS_KEY_ID=my_access_key AWS_SECRET_ACCESS_KEY=my_secret_key imgproxy
4444

4545
# same for Docker
46-
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it darthsim/imgproxy
46+
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it ghcr.io/imgproxy/imgproxy
4747
```
4848

4949
#### Shared credentials file

docusaurus.config.ts

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -193,8 +193,8 @@ const config: Config = {
193193
href: "https://github.com/imgproxy",
194194
},
195195
{
196-
label: "DockerHub",
197-
href: "https://hub.docker.com/r/darthsim/imgproxy/",
196+
label: "Docker",
197+
href: "https://github.com/imgproxy/imgproxy/pkgs/container/imgproxy",
198198
},
199199
{
200200
label: "Sponsor imgproxy",

versioned_docs/version-3.19.x/configuration/loading_environment_variables.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ You can specify an AWS Access Key ID and a Secret Access Key by setting the stan
5050
AWS_ACCESS_KEY_ID=my_access_key AWS_SECRET_ACCESS_KEY=my_secret_key imgproxy
5151

5252
# same for Docker
53-
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it darthsim/imgproxy
53+
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it ghcr.io/imgproxy/imgproxy
5454
```
5555

5656
#### Shared credentials file
@@ -108,7 +108,7 @@ You can specify an AWS Access Key ID and a Secret Access Key by setting the stan
108108
AWS_ACCESS_KEY_ID=my_access_key AWS_SECRET_ACCESS_KEY=my_secret_key imgproxy
109109

110110
# same for Docker
111-
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it darthsim/imgproxy
111+
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it ghcr.io/imgproxy/imgproxy
112112
```
113113

114114
#### Shared credentials file

versioned_docs/version-3.19.x/getting_started.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@ This guide will show you how to quickly resize your first image using imgproxy.
1111
Let's assume you already have Docker installed on your machine — you can pull an official imgproxy Docker image, and you’re done!
1212

1313
```bash
14-
docker pull darthsim/imgproxy:latest
15-
docker run -p 8080:8080 -it darthsim/imgproxy
14+
docker pull ghcr.io/imgproxy/imgproxy:latest
15+
docker run -p 8080:8080 -it ghcr.io/imgproxy/imgproxy:latest
1616
```
1717

1818
If you don't have docker or if you want to deploy imgproxy to a cloud, you can check out our [installation guide](./installation.mdx) for more installation options.

versioned_docs/version-3.19.x/image_sources/amazon_s3.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ You can specify an AWS Access Key ID and a Secret Access Key by setting the stan
4040
AWS_ACCESS_KEY_ID=my_access_key AWS_SECRET_ACCESS_KEY=my_secret_key imgproxy
4141

4242
# same for Docker
43-
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it darthsim/imgproxy
43+
docker run -e AWS_ACCESS_KEY_ID=my_access_key -e AWS_SECRET_ACCESS_KEY=my_secret_key -it ghcr.io/imgproxy/imgproxy
4444
```
4545

4646
#### Shared credentials file

0 commit comments

Comments
 (0)