Skip to content

Commit 1fb7f49

Browse files
committed
Remove deploy to Dome docs; It seems to be down
1 parent b639600 commit 1fb7f49

9 files changed

Lines changed: 0 additions & 54 deletions

File tree

docs/installation.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -82,12 +82,6 @@ You can find a step-by-step guide on how to deploy imgproxy to AWS Lambda in [ou
8282

8383
You can deploy imgproxy to AWS ECS using the [official imgproxy CloudFormation template](https://github.com/imgproxy/imgproxy-cloudformation).
8484

85-
### Dome
86-
87-
imgproxy can be deployed to [Dome](https://trydome.io/) with the click of a button:
88-
89-
[![Deploy to Dome](https://trydome.io/button.svg)](https://app.trydome.io/signup?package=imgproxy)
90-
9185
## Packages
9286

9387
### Building Linux packages

versioned_docs/version-3.19.x/installation.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -74,12 +74,6 @@ Take a note that the example is using a tag suffixed with `-amd64` when pulling
7474
If the machine where you're running these commands uses an `ARM64` CPU (such as Apple Silicone ones) and you don't use the `-amd64` suffix, `docker pull` will download an image built for the `ARM64` CPU architecture, and it won't be able to launch on Heroku.
7575
:::
7676

77-
### Dome
78-
79-
imgproxy can be deployed to [Dome](https://trydome.io/) with the click of a button:
80-
81-
[![Deploy to Dome](https://trydome.io/button.svg)](https://app.trydome.io/signup?package=imgproxy)
82-
8377
## Packages
8478

8579
### Arch Linux and derivatives

versioned_docs/version-3.20.x/installation.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -74,12 +74,6 @@ Take a note that the example is using a tag suffixed with `-amd64` when pulling
7474
If the machine where you're running these commands uses an `ARM64` CPU (such as Apple Silicone ones) and you don't use the `-amd64` suffix, `docker pull` will download an image built for the `ARM64` CPU architecture, and it won't be able to launch on Heroku.
7575
:::
7676

77-
### Dome
78-
79-
imgproxy can be deployed to [Dome](https://trydome.io/) with the click of a button:
80-
81-
[![Deploy to Dome](https://trydome.io/button.svg)](https://app.trydome.io/signup?package=imgproxy)
82-
8377
## Packages
8478

8579
### Arch Linux and derivatives

versioned_docs/version-3.21.x/installation.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -74,12 +74,6 @@ Take a note that the example is using a tag suffixed with `-amd64` when pulling
7474
If the machine where you're running these commands uses an `ARM64` CPU (such as Apple Silicone ones) and you don't use the `-amd64` suffix, `docker pull` will download an image built for the `ARM64` CPU architecture, and it won't be able to launch on Heroku.
7575
:::
7676

77-
### Dome
78-
79-
imgproxy can be deployed to [Dome](https://trydome.io/) with the click of a button:
80-
81-
[![Deploy to Dome](https://trydome.io/button.svg)](https://app.trydome.io/signup?package=imgproxy)
82-
8377
## Packages
8478

8579
### Arch Linux and derivatives

versioned_docs/version-3.22.x/installation.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -74,12 +74,6 @@ Take a note that the example is using a tag suffixed with `-amd64` when pulling
7474
If the machine where you're running these commands uses an `ARM64` CPU (such as Apple Silicone ones) and you don't use the `-amd64` suffix, `docker pull` will download an image built for the `ARM64` CPU architecture, and it won't be able to launch on Heroku.
7575
:::
7676

77-
### Dome
78-
79-
imgproxy can be deployed to [Dome](https://trydome.io/) with the click of a button:
80-
81-
[![Deploy to Dome](https://trydome.io/button.svg)](https://app.trydome.io/signup?package=imgproxy)
82-
8377
## Packages
8478

8579
### Arch Linux and derivatives

versioned_docs/version-3.23.x/installation.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -74,12 +74,6 @@ Take a note that the example is using a tag suffixed with `-amd64` when pulling
7474
If the machine where you're running these commands uses an `ARM64` CPU (such as Apple Silicone ones) and you don't use the `-amd64` suffix, `docker pull` will download an image built for the `ARM64` CPU architecture, and it won't be able to launch on Heroku.
7575
:::
7676

77-
### Dome
78-
79-
imgproxy can be deployed to [Dome](https://trydome.io/) with the click of a button:
80-
81-
[![Deploy to Dome](https://trydome.io/button.svg)](https://app.trydome.io/signup?package=imgproxy)
82-
8377
## Packages
8478

8579
### Arch Linux and derivatives

versioned_docs/version-3.24.x/installation.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -74,12 +74,6 @@ Take a note that the example is using a tag suffixed with `-amd64` when pulling
7474
If the machine where you're running these commands uses an `ARM64` CPU (such as Apple Silicone ones) and you don't use the `-amd64` suffix, `docker pull` will download an image built for the `ARM64` CPU architecture, and it won't be able to launch on Heroku.
7575
:::
7676

77-
### Dome
78-
79-
imgproxy can be deployed to [Dome](https://trydome.io/) with the click of a button:
80-
81-
[![Deploy to Dome](https://trydome.io/button.svg)](https://app.trydome.io/signup?package=imgproxy)
82-
8377
## Packages
8478

8579
### Arch Linux and derivatives

versioned_docs/version-3.25.x/installation.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -74,12 +74,6 @@ Take a note that the example is using a tag suffixed with `-amd64` when pulling
7474
If the machine where you're running these commands uses an `ARM64` CPU (such as Apple Silicone ones) and you don't use the `-amd64` suffix, `docker pull` will download an image built for the `ARM64` CPU architecture, and it won't be able to launch on Heroku.
7575
:::
7676

77-
### Dome
78-
79-
imgproxy can be deployed to [Dome](https://trydome.io/) with the click of a button:
80-
81-
[![Deploy to Dome](https://trydome.io/button.svg)](https://app.trydome.io/signup?package=imgproxy)
82-
8377
## Packages
8478

8579
### Arch Linux and derivatives

versioned_docs/version-3.26.x/installation.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -82,12 +82,6 @@ You can find a step-by-step guide on how to deploy imgproxy to AWS Lambda in [ou
8282

8383
You can deploy imgproxy to AWS ECS using the [official imgproxy CloudFormation template](https://github.com/imgproxy/imgproxy-cloudformation).
8484

85-
### Dome
86-
87-
imgproxy can be deployed to [Dome](https://trydome.io/) with the click of a button:
88-
89-
[![Deploy to Dome](https://trydome.io/button.svg)](https://app.trydome.io/signup?package=imgproxy)
90-
9185
## Packages
9286

9387
### Building Linux packages

0 commit comments

Comments
 (0)