←back to thread

Replacing a $3000/mo Heroku bill with a $55/mo server

(disco.cloud)
804 points jryio | 2 comments | 21 Oct 25 20:28 UTC | HN request time: 0.001s | source
Show context
pentacent_hq ◴[21 Oct 25 21:36 UTC] No.45662029[source]▶
Cool project!

From looking at your docs, it appears like using and connecting GitHub is a necessary prerequisite for using Disco. Is that correct? Can disco also deploy an existing Docker image in a registry of my choosing without a build step? (Something like this with Kamal: `kamal --skip-push --version latest`)

replies(1): >>45662096 #
1. gregsadetsky ◴[21 Oct 25 21:43 UTC] No.45662096[source]▶
Correct, GitHub is necessary at this point to deploy code.

However, yes, you can ask Disco to fetch an existing Docker image (we use that to self-host RabbitMQ). An example of deploying Meilisearch's image is here [0] with the tutorial here [1].

Do you typically build your Docker images and push them to a registry? Curious to learn more about your deployment process.

[0] https://github.com/letsdiscodev/sample-meilisearch/blob/main...

[1] https://disco.cloud/docs/deployment-guides/meilisearch

replies(1): >>45665332 #
2. pentacent_hq ◴[22 Oct 25 05:54 UTC] No.45665332[source]▶
Yes, I try to keep my CI pipelines somewhat platform-agnostic so even though I'm mostly using GitHub, my workflow is typically to first build a Docker image and push it to a registry, then use Kamal to deploy that image.