From 844670421f4df7efdb9a7c57652279e948c2abdc Mon Sep 17 00:00:00 2001 From: GeoSegun Date: Thu, 23 Oct 2025 13:22:45 +0100 Subject: [PATCH] Add Seenode deployment option --- guides/deployment/deployment.md | 1 + 1 file changed, 1 insertion(+) diff --git a/guides/deployment/deployment.md b/guides/deployment/deployment.md index 691f07bbe4..e5dda70899 100644 --- a/guides/deployment/deployment.md +++ b/guides/deployment/deployment.md @@ -148,3 +148,4 @@ The reason for this is simple. While a WebSocket is a long-lived open connection * [Render](https://render.com) has first class support for Phoenix applications. There are guides for hosting Phoenix with [Mix releases](https://render.com/docs/deploy-phoenix) and as a [Distributed Elixir Cluster](https://render.com/docs/deploy-elixir-cluster). * [Railway](https://railway.com) also provides support for Phoenix applications using [Mix releases](https://docs.railway.com/guides/phoenix). + * [Seenode](https://seenode.com) provides first class support for Phoenix with [a detailed documentation](https://seenode.com/docs/frameworks/elixir/phoenix/) and a [quickstart template](https://github.com/seenode/example-phoenix).