NocoDB utilzes a spreadsheet UI for creating online databases, either from scratch or by connecting to an existing Postgres or MySQL database. It has use cases in CRM, project management, operations, and inventory.
Requires application load balancer
Running NocoDB on FlexStack requires an Application Load Balancer which incurs an additional fee of around $16/month per environment. The ALB is necessary for communicating over websockets, which are not supported by API Gateway HTTP APIs.
Features
- Connect with external DB
- Realtime collaboration
- Schema management
- REST API and integrations
Variables
DATABASE_URL: Optional By default this app will create a SQLite database that will persist between reboots. Alternatively, you can provide a JDBC-style PostgreSQL connection URI for the database you want to use as a backend and apply NocoDB migrations to. Check out the FlexStack Databases guide for integration recommendations. Below is a screenshot of a copyable JDBC connection URI in the Neon dashboard.
Getting started
Once your app is deployed, open its URL in your browser. From there you'll sign up with a Super Admin account.
Additional configuration
NocoDB can be configured by adding environment variables to your deplyoment. Some you may want to set right away are listed below:
| Name | Description |
|---|---|
| NC_PUBLIC_URL | This is the base URL used for constructing URLs in email templates, generating the Swagger documentation URL, and handling backend URL requirements. It should be set to your public-facing NocoDB URL to ensure consistency across the application. You can set this to your CloudFront URL e.g. https://dxxxxxx.cloudfront.net or use a custom domain. |
| NC_REDIS_URL | Use a Redis URL for external caching. Eg: redis://:[email protected]:6380/4 |