Skip to content

Commit 9bb0634

Browse files
committed
chore(installtion): add render
1 parent 1b78e38 commit 9bb0634

File tree

2 files changed

+35
-0
lines changed

2 files changed

+35
-0
lines changed

content/self-hosting/installation/meta.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@
1313
"gcp-cloud-run",
1414
"digital-ocean",
1515
"k8s",
16+
"render",
1617

1718
"nginx",
1819
"apache",
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: 'Install on Render'
3+
tags: ['render', 'docker']
4+
keywords: ['NocoDB Render', 'Install NocoDB', 'NocoDB Docker']
5+
---
6+
7+
> ⚠️ For optimal performance, we recommend using the \$25/month "Standard" service on Render.
8+
9+
Click below to instantly launch NocoDB on Render:
10+
11+
[![Deploy to Render](https://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy?repo=https://github.com/nocodb/nocodb)
12+
13+
If needed, enter the repo URL manually:
14+
`https://github.com/nocodb/nocodb`.
15+
Once deployment is complete, your NocoDB instance will be accessible via the Render-provided URL.
16+
17+
## File Storage via S3
18+
19+
Uploaded files are stored locally by default, configure an S3-compatible storage service by setting these environment variables
20+
21+
* `NC_S3_ACCESS_KEY`
22+
* `NC_S3_ACCESS_SECRET`
23+
* `NC_S3_BUCKET_NAME`
24+
* `NC_S3_REGION`
25+
* `NC_S3_ENDPOINT`
26+
27+
## Keeping Your Deployment Updated
28+
29+
To pull the latest NocoDB updates:
30+
31+
1. Open the Render dashboard for your NocoDB service.
32+
2. Click **Manual Deploy****Deploy latest commit**.
33+
34+
This ensures your deployment stays in sync with the latest improvements.

0 commit comments

Comments
 (0)