diff --git a/docs/self-hosting/deployment-options/aws-ec2.mdx b/docs/self-hosting/deployment-options/aws-ec2.mdx deleted file mode 100644 index 303df2009..000000000 --- a/docs/self-hosting/deployment-options/aws-ec2.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: "AWS EC2" -description: "Learn to install Infisical on EC2 using Cloud Formation template" ---- - - -This deployment option will use AWS Cloudformation to auto deploy an instance of Infisical on a single EC2 via Docker Compose. - -**Resources that will be provisioned** -- 1 EC2 instance -- 1 DocumentDB cluster -- 1 DocumentDB instance -- Security groups - - -Once installation is complete, you will have to create the first account. No default account is provided. - - - - - \ No newline at end of file diff --git a/docs/self-hosting/deployment-options/aws-lightsail.mdx b/docs/self-hosting/deployment-options/aws-lightsail.mdx deleted file mode 100644 index b5cdb6c9d..000000000 --- a/docs/self-hosting/deployment-options/aws-lightsail.mdx +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: "AWS Lightsail" -description: "Deploy Infisical with AWS Lightsail" ---- - -Prerequisites: -- Have an account with [Amazon Web Services (AWS)](https://aws.amazon.com/) - - - - 1.1. In AWS, navigate to the **Lightsail** service and press **Create container service** under the **Containers** tab. - ![AWS Lightsail](/images/self-hosting/deployment-options/aws-lightsail/awsl-select-lightsail.png) - - ![AWS Lightsail create container service](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service.png) - - 1.2. In the **Container service location** section, select the AWS region that's closest to your infrastructure. - - Afterwards, in the **Container service capacity** section, set the power level and scale to fit your needs; you may opt for the default setting - and adjust accordingly in the future. - - ![AWS Lightsail container service capacity](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service-capacity.png) - - 1.3. In the **Set up your first deployment** section, select the **Specify a custom deployment** option. Give the container a friendly name like **infisical** and fill in your intended [Infisical public Docker image](https://hub.docker.com/r/infisical/infisical) in the **Image** field; this will pull the image from Docker Hub. - - For example, in order to opt for Infisical `v0.43.4`, you would input: `infisical/infisical:v0.43.4`. - - ![AWS Lightsail container service deployment](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service-deployment.png) - - 1.4. Running Infisical requires a few environment variables to be set for the container service. - At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL` - which you can read more about [here](/self-hosting/configuration/envars). - - In the **Environment variables** section, fill in the required environment variables. - - - To use more features like emailing and single sign-on, you can set additional configuration options [here](/self-hosting/configuration/envars). - - - Also, under the **Open ports** section, add an entry for port `8080` and protocol `HTTP` since Infisical listens on port `8080`. - - ![AWS Lightsail container service environment variables](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service-envars.png) - - 1.5. In the **Public endpoint** section, select the container from the previous steps from the dropdown; this will make the container accessible over the public internet. - - ![AWS Lightsail container service public endpoint](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service-public-endpoint.png) - - 1.6. Finally, in the **Identify your service** section, give the container service a unique name like infisical and press **Create container service**. - - ![AWS Lightsail container service summary](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service-summary.png) - - - On the newly-created container service page, wait for the **Status** to turn to **Running** and check out the **Public domain** of the container service; you can access your instance of Infisical by this URL. - - ![AWS Lightsail container service overview](/images/self-hosting/deployment-options/aws-lightsail/awsl-container-service-overview.png) - - - - - - Yes, here are a few that come to mind: - - In step 1.3, we recommend pinning the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags) - instead of referring to the `latest` tag to avoid any unexpected version-to-version migration issues. - - We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned! - - \ No newline at end of file diff --git a/docs/self-hosting/deployment-options/azure-app-services.mdx b/docs/self-hosting/deployment-options/azure-app-services.mdx deleted file mode 100644 index a8472ae2b..000000000 --- a/docs/self-hosting/deployment-options/azure-app-services.mdx +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: "Azure App Services" -description: "Deploy Infisical with Azure App Service" ---- - -Prerequisites: - - Have an account with [Microsoft Azure](https://azure.microsoft.com/en-us) - - - - 1.1. In Azure, navigate to the **App Services** solution and press **Create > Web App**. - - ![Azure app services](/images/self-hosting/deployment-options/azure-app-services/aas-select-app-services.png) - - ![Azure create app service](/images/self-hosting/deployment-options/azure-app-services/aas-create-app-service.png) - - 1.2. In the **Basics** section, specify the **Subscription** and **Resource group** to manage the deployed resource. - - Also, give the container a friendly name like Infisical and specify a **Region** for it to be deployed to. - - ![Azure app service basics](/images/self-hosting/deployment-options/azure-app-services/aas-create-app-service-basics.png) - - 1.3. In the **Docker** section, select the **Single Container** option under **Options** and specify **Docker Hub** as the image source - - Next, under the **Docker hub options** sub-section, select the **Public** option under **Access Type** and fill in your intended [Infisical public Docker image](https://hub.docker.com/r/infisical/infisical) in the **Image and tag** field; this will pull the image from Docker Hub. - - For example, in order to opt for Infisical `v0.43.4`, you would input: `infisical/infisical:v0.43.4`. - - ![Azure app service docker](/images/self-hosting/deployment-options/azure-app-services/aas-create-app-service-docker.png) - - 1.4. Finally, in the **Review + create** section, double check the information from the previous steps and press **Create** to create the Azure app service. - - ![Azure app service review](/images/self-hosting/deployment-options/azure-app-services/aas-create-app-service-review.png) - - 1.5. Next, wait a minute or two on the deployment overview page for the app to be created. Once the deployment is complete, press **Go to resource** - to head to the **App Service dashboard** for the newly-created app. - - ![Azure app service deployment complete](/images/self-hosting/deployment-options/azure-app-services/aas-app-service-deployment-complete.png) - - 1.6. Running Infisical requires a few environment variables to be set for the Azure app service. - At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL` - which you can read more about [here](/self-hosting/configuration/envars). - - - To use more features like emailing and single sign-on, you can set additional configuration options [here](/self-hosting/configuration/envars). - - - Additionally, you must set the variable `WEBSITES_PORT=8080` since - Infisical listens on port `8080`. - - In the **Settings > Configuration** section of the newly-created app service, fill in the required environment variables. - - ![Azure app service deployment complete](/images/self-hosting/deployment-options/azure-app-services/aas-app-service-configuration.png) - - - In the **Overview** section, check out the **Default domain** for your instance of Infisical; you can visit the instance at this URL. - - ![Azure app service deployment complete](/images/self-hosting/deployment-options/azure-app-services/aas-app-service-overview.png) - - - - - - Yes, here are a few that come to mind: - - In step 1.3, we recommend pinning the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags) - instead of referring to the `latest` tag to avoid any unexpected version-to-version migration issues. - - In step 1.2, we recommend selecting a **Region** option that is closest to your infrastructure/clients to reduce latency. - - We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned! - - \ No newline at end of file diff --git a/docs/self-hosting/deployment-options/azure-container-instances.mdx b/docs/self-hosting/deployment-options/azure-container-instances.mdx deleted file mode 100644 index 05e877f37..000000000 --- a/docs/self-hosting/deployment-options/azure-container-instances.mdx +++ /dev/null @@ -1,88 +0,0 @@ ---- -title: "Azure Container Instances" -description: "Deploy Infisical with Azure Container Instances" ---- - -Prerequisites: -- Have an account with [Microsoft Azure](https://azure.microsoft.com/en-us) - - - This brief goes over how to deploy an instance of Infisical with Azure Container Instances without TLS/SSL configuration. - - There are various options for enabling TLS/SSL with Azure Container Instances more suitable for production including: - - [Enabling a TLS endpoint in a sidecar container](https://learn.microsoft.com/en-us/azure/container-instances/container-instances-container-group-ssl). - - [Enabling automatic HTTPS with Caddy in a sidecar container](https://learn.microsoft.com/en-us/azure/container-instances/container-instances-container-group-automatic-ssl). - - Using Azure Function Proxies, Application Gateway, etc. - - For a simpler deployment experience with complete TLS/SSL setup, you may try [deploying Infisical with Azure App Services](/self-hosting/deployment-options/azure-app-services). - - - - - 1.1. In Azure, navigate to the **Container Instances** solution and press **Create**. - - ![Azure container instance](/images/self-hosting/deployment-options/azure-container-instances/aci-select-container-instances.png) - - ![Azure create container instance](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance.png) - - 1.2. In the **Basics** section, specify the **Subscription** and **Resource group** to manage the deployed resource. - - Also, give the container a friendly name like Infisical and specify a **Region** for it to be deployed to. - - ![Azure container instance basics](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance-basics-1.png) - - Next, select the **Public** option under **Image type** and fill in your intended [Infisical public Docker image](https://hub.docker.com/r/infisical/infisical) in the **Image** field; this will pull the image from Docker Hub. - - For example, in order to opt for Infisical `v0.43.4`, you would input: `infisical/infisical:v0.43.4`. - - ![Azure container instance basics](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance-basics-2.png) - - - Depending on your use-case and requirements, you may find it helpful to further configure your Azure container instance. - - For example, you may want to adjust the **Region** option to specify which region to deploy the container for your - instance of Infisical to minimize distance and therefore latency between the instance and your infrastructure. - - - 1.3. In the **Networking** section, select the **Public** option under **Networking type**; this will make the container accessible over the public internet. - - Next, under the **Ports** section, add an entry for port `8080` and protocol `TCP` since Infisical listens on port `8080`. - - ![Azure container instance networking](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance-networking.png) - - 1.4. Running Infisical requires a few environment variables to be set for the Azure container instance. - At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL` - which you can read more about [here](/self-hosting/configuration/envars). - - In the **Advanced** section, fill in the required environment variables. - - - To use more features like emailing and single sign-on, you can set additional configuration options [here](/self-hosting/configuration/envars). - - - ![Azure container instance advanced](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance-advanced.png) - - 1.5. Finally, in the **Review + create** section, double check the information from the previous steps and press **Create** to create the Azure container instance. - - ![Azure container instance review](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance-review.png) - - - Head to the **Overview** page of the newly-created container instance to view its **IP address (Public)**; you can access your instance of Infisical by this IP address under the port `:8080`. - - For example, in the image below, the IP address of the sample deployed container instance is `4.255.87.109`; the instance would be accessible in the browser by heading to `4.255.87.109:8080`. - - ![Azure container instance overview](/images/self-hosting/deployment-options/azure-container-instances/aci-container-instance-overview.png) - - - - - - Yes, here are a few that come to mind: - - In step 1.2, we recommend pinning the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags) - instead of referring to the `latest` tag to avoid any unexpected version-to-version migration issues. - - In step 1.2, we recommend selecting a **Region** option that is closest to your infrastructure/clients to reduce latency. - - Enable TLS/SSL with Azure Container Instances. There are various options for doing so including [enabling a TLS endpoint in a sidecar container](https://learn.microsoft.com/en-us/azure/container-instances/container-instances-container-group-ssl), [enabling automatic HTTPS with Caddy in a sidecar container](https://learn.microsoft.com/en-us/azure/container-instances/container-instances-container-group-automatic-ssl), and using Azure Function Proxies, Application Gateway, etc. - - We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned! - - \ No newline at end of file diff --git a/docs/self-hosting/deployment-options/digital-ocean-marketplace.mdx b/docs/self-hosting/deployment-options/digital-ocean-marketplace.mdx deleted file mode 100644 index f1e739f08..000000000 --- a/docs/self-hosting/deployment-options/digital-ocean-marketplace.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: "Digital Ocean" -description: "Learn to install Infisical on Digital Ocean" ---- - -Infisical can be deployed on a Kubernetes cluster with a single click through our Digital Ocean marketplace application. -The initiation of the installation process triggers the creation of a Kubernetes cluster, followed by the installation of Infisical onto that cluster. - -This automated deployment method uses the same process under the hood as the manual [Kubernetes installation guide](./kubernetes-helm). - -### Initiate the installation - -To start the process, click the following button and follow the instructions there. - - - - - -### Access Infisical Web -Once the installation finishes, head to the `Networking` section via the sidebar and select `Load Balancers`. -Within this section, you'll find the newly created load balancer for Infisical. You can access Infisical at the IP address allocated to that load balancer. - -### Adjusting configurations -If you need to either upgrade or downgrade Infisical, or modify environment variables to alter its functionality, refer to our [Kubernetes installation](./kubernetes-helm) page for detailed instructions. - -Because Digital Ocean deploys the same Helm application as described in our [Kubernetes installation](./kubernetes-helm) guide, you can utilize that guide to implement the required changes. -It's important to note that any modifications requires familiarly with Helm package manager. diff --git a/docs/self-hosting/deployment-options/fly.io.mdx b/docs/self-hosting/deployment-options/fly.io.mdx deleted file mode 100644 index dacd9476b..000000000 --- a/docs/self-hosting/deployment-options/fly.io.mdx +++ /dev/null @@ -1,108 +0,0 @@ ---- -title: "Fly.io" -description: "Deploy Infisical with Fly.io" ---- - -Prerequisites: -- Have an account with [Fly.io](https://fly.io/) -- Have installed the [Fly.io CLI](https://fly.io/docs/hands-on/install-flyctl/) - - - - In your terminal, run the following command from the source directory of your project to create a new Fly.io app - with a `fly.toml` configuration file: - - ``` - fly launch - ``` - - - Add a **build** section to the `fly.toml` file to specify the [Infisical public Docker image](https://hub.docker.com/r/infisical/infisical): - - ``` - [build] - image = "infisical/infisical:v0.43.4" - ``` - - Afterwards, your `fly.toml` file should look similar to: - - ``` - app = "infisical" - primary_region = "lax" - - [http_service] - internal_port = 8080 - force_https = true - auto_stop_machines = true - auto_start_machines = true - min_machines_running = 0 - processes = ["app"] - - [[vm]] - cpu_kind = "shared" - cpus = 1 - memory_mb = 1024 - - [build] - image = "infisical/infisical:v0.43.4" - ``` - - - Depending on your use-case and requirements, you may find it helpful to further configure your `fly.toml` file - with options [here](https://fly.io/docs/reference/configuration/). - - For example, you may want to adjust the `primary-region` option to specify which [region](https://fly.io/docs/reference/regions/) to create the new machine for your - instance of Infisical to minimize distance and therefore latency between the instance and your infrastructure. - - - - - Running Infisical requires a few environment variables to be set on the Fly.io machine. - At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL` - which you can read more about [here](/self-hosting/configuration/envars). - - For this step, we recommend setting the variables as Fly.io [app secrets](https://fly.io/docs/reference/secrets/) which - are made available to the app as environment variables. You can set the variables either via the Fly.io CLI or project [dashboard](https://fly.io/dashboard). - - - - Run the following command (with each `VALUE` replaced) in the source directory of your project to set the required variables: - - ``` - flyctl secrets set ENCRYPTION_KEY=VALUE AUTH_SECRET=VALUE MONGO_URL=VALUE REDIS_URL=VALUE... - ``` - - - In Fly.io, head to your Project > Secrets and add the required variables. - - ![Fly.io deployment secrets](/images/self-hosting/deployment-options/flyio/flyio-secrets.png) - - - - - To use more features like emailing and single sign-on, you can set additional configuration options [here](/self-hosting/configuration/envars). - - - - Finally, run the following command in the source directory of your project to deploy your Infisical instance on Fly.io - with the updated `fly.toml` configuration file from step 2 and secrets from step 3: - - ``` - fly deploy - ``` - - - - - - Yes, here are a few that come to mind: - - In step 2, we recommend pinning the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags) - instead of referring to the `latest` tag to avoid any unexpected version-to-version migration issues. - - In step 2, we recommend selecting a `primary_region` option that is closest to your infrastructure/clients to reduce latency; a full list of regions supported by Fly.io can be found [here](https://fly.io/docs/reference/regions/). - - We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned! - - - -Resources: -- [Fly.io documentation](https://fly.io/docs/) \ No newline at end of file diff --git a/docs/self-hosting/deployment-options/gcp-cloud-run.mdx b/docs/self-hosting/deployment-options/gcp-cloud-run.mdx deleted file mode 100644 index 67c9fcf57..000000000 --- a/docs/self-hosting/deployment-options/gcp-cloud-run.mdx +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: "GCP Cloud Run" -description: "Deploy Infisical with GCP Cloud Run" ---- - -Prerequisites: -- Have an account with [Google Cloud Platform (GCP)](https://cloud.google.com/) - - - - In GCP, create a new project and give it a friendly name like Infisical. - - ![GCP create project](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-create-project.png) - - ![GCP create project](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-create-project-2.png) - - - 2.1. Inside the GCP project, navigate to the **Cloud Run** product and create a new service. - - ![GCP Cloud Run](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-select-cloud-run.png) - - ![GCP Cloud Run create service](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-create-service.png) - - 2.2. In the service creation form, select the **Deploy one revision from an existing container image** option and fill in your intended [Infisical public Docker image](https://hub.docker.com/r/infisical/infisical) in the container image URL. - - For example, in order to opt for Infisical `v0.43.4`, you would input: `docker.io/infisical/infisical:v0.43.4`. - - ![GCP Cloud Run create service docker image specification](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-create-service-docker-image.png) - - 2.3. Running Infisical requires a few environment variables to be set for the GCP Cloud Run service. - At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL` - which you can read more about [here](/self-hosting/configuration/envars). - - For this step, fill in the required environment variables in the Edit Container > Variables & Secrets > Environment variables section. - - - To use more features like emailing and single sign-on, you can set additional configuration options [here](/self-hosting/configuration/envars). - - - ![GCP Cloud Run create service environment variable specification](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-create-service-envars.png) - - - Depending on your use-case and requirements, you may find it helpful to further configure your GCP Cloud Run service. - - For example, you may want to adjust the **Region** option to specify which region to deploy the underlying container for your - instance of Infisical to minimize distance and therefore latency between the instance and your infrastructure. - - - Finally, press **Create** to finish setting up the GCP Cloud Run service. - - - Head to the **Service details** of the newly-created service to view its URL; you can access your instance of Infisical by clicking on the URL. - - ![GCP Cloud Run service details](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-service-details.png) - - - - - - Yes, here are a few that come to mind: - - In step 2, we recommend pinning the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags) - instead of referring to the `latest` tag to avoid any unexpected version-to-version migration issues. - - In step 2, we recommend selecting a **Region** option that is closest to your infrastructure/clients to reduce latency. - - We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned! - - \ No newline at end of file diff --git a/docs/self-hosting/deployment-options/railway.mdx b/docs/self-hosting/deployment-options/railway.mdx deleted file mode 100644 index 29d2ce293..000000000 --- a/docs/self-hosting/deployment-options/railway.mdx +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: "Railway" -description: "Deploy Infisical with Railway" ---- - -Prerequisites: -- Have an account with [Railway](https://railway.app/) - - - - 1.1. In Railway, create a new project and select **Deploy a template > Infisical**. - - ![Railway create project](/images/self-hosting/deployment-options/railway/railway-create-project.png) - - ![Railway deploy template](/images/self-hosting/deployment-options/railway/railway-deploy-template.png) - - ![Railway deploy template infisical](/images/self-hosting/deployment-options/railway/railway-deploy-template-infisical.png) - - ![Railway template overview](/images/self-hosting/deployment-options/railway/railway-template-overview.png) - - 1.2. At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL` - which you can read more about [here](/self-hosting/configuration/envars). - - By default, the Infisical template on Railway pre-configures environment variables on each service in the deployment but requires you to supply two for the Redis and MongoDB services. - - On the MongoDB service, supply a value for the `MONGO_INITDB_ROOT_PASSWORD` variable. - - ![Railway template MongoDB configuration](/images/self-hosting/deployment-options/railway/railway-template-mongodb.png) - - On the Redis service, supply a value for the `REDIS_PASSWORD` variable. - - ![Railway template Redis configuration](/images/self-hosting/deployment-options/railway/railway-template-redis.png) - - ![Railway template Redis configuration](/images/self-hosting/deployment-options/railway/railway-template-redis.png) - - - To use more features like emailing and single sign-on, you can set additional configuration options on the Infisical service [here](/self-hosting/configuration/envars). - - - Finally, press **Deploy** to create the project and deploy the services within it. - - ![Railway template Infisical configuration](/images/self-hosting/deployment-options/railway/railway-template-infisical.png) - - ![Railway Infisical architecture](/images/self-hosting/deployment-options/railway/railway-infisical-architecture.png) - - - Head to the newly-created Infisical service to view its URL under Networking > Public Networking; you can access your instance of Infisical by clicking on the URL. - - ![Railway Infisical service](/images/self-hosting/deployment-options/railway/railway-infisical-service.png) - - - - - - Yes, here are a few that come to mind: - - While the Infisical template on Railway uses the `latest` tag to get the latest version of Infisical, we recommend creating a Railway deployment that pins the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags) to avoid any unexpected version-to-version migration issues. - - We recommend selecting **Deployment region** options for your Railway service deployments to be closest to your infrastructure/clients to reduce latency. - - We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned! - - \ No newline at end of file diff --git a/docs/self-hosting/deployment-options/render.mdx b/docs/self-hosting/deployment-options/render.mdx deleted file mode 100644 index 17faf060a..000000000 --- a/docs/self-hosting/deployment-options/render.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: "Render.com" -description: "Learn to install Infisical Render.com" ---- - -**Prerequisites** -- An account at Render.com -- A document DB instance - -Deploying on Render is one of the quickest ways to have Infisical running in production. -Before you start deployment, you will need to obtain document db connection string. This will be used for `MONGO_URL` environment variable required during installation. - -You can create a document db database using services such as [MongoDB](https://www.mongodb.com/), [AWS DocumentDB](https://aws.amazon.com/documentdb/), and others. Once done, click the link below to start deployment. - -### **[Deploy to Render](https://render.com/deploy?repo=https://github.com/Infisical/infisical)** - -# - - -Once installation is complete, you will have to create the first account. No default account is provided. - \ No newline at end of file