From ba484d938fd8d7b1296e45cc97f319b752a9c6a4 Mon Sep 17 00:00:00 2001 From: agneliutkiene Date: Fri, 20 Feb 2026 17:26:29 +0200 Subject: [PATCH] docs(deployment): include Hostinger in production environment examples --- content/deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/deployment.md b/content/deployment.md index 54ff2eca81..b18fc19b50 100644 --- a/content/deployment.md +++ b/content/deployment.md @@ -35,7 +35,7 @@ Upon successful compilation, you should see a `dist` directory in your project r #### Production environment -Your production environment is where your application will be accessible to external users. This could be a cloud-based platform like [AWS](https://aws.amazon.com/) (with EC2, ECS, etc.), [Azure](https://azure.microsoft.com/), or [Google Cloud](https://cloud.google.com/), or even a dedicated server you manage, such as [Hetzner](https://www.hetzner.com/). +Your production environment is where your application will be accessible to external users. This could be a cloud-based platform like [AWS](https://aws.amazon.com/) (with EC2, ECS, etc.), [Azure](https://azure.microsoft.com/), or [Google Cloud](https://cloud.google.com/), or even a dedicated server you manage, such as [Hetzner](https://www.hetzner.com/), or a managed Node.js option like [Hostinger Web Apps Hosting](https://www.hostinger.com/web-apps-hosting). To simplify the deployment process and avoid manual setup, you can use a service like [Mau](https://mau.nestjs.com/ 'Deploy Nest'), our official platform for deploying NestJS applications on AWS. For more details, check out [this section](todo).