NocoDB

• Instalação e Configuração NocoDB
• Instalação NocoDB
• Instalação customizada NocoDB

Instalação e Configuração NocoDB

Instalação NocoDB

Link: https://hub.docker.com/r/nocodb/nocodb
https://github.com/nocodb/nocodb                 git clone https://github.com/nocodb/nocodb.git

NocoDB is the fastest and easiest way to build databases online.

Website • Discord • Community • Twitter • Reddit • Documentation

See other languages »

Join Our Community

Installation

Docker with SQLite

docker run -d \
  --name noco \
  -v "$(pwd)"/nocodb:/usr/app/data/ \
  -p 8080:8080 \
  nocodb/nocodb:latest

Docker with PG

docker run -d \
  --name noco \
  -v "$(pwd)"/nocodb:/usr/app/data/ \
  -p 8080:8080 \
  -e NC_DB="pg://host.docker.internal:5432?u=root&p=password&d=d1" \
  -e NC_AUTH_JWT_SECRET="569a1821-0a93-45e8-87ab-eb857f20a010" \
  nocodb/nocodb:latest

Nix

nix run github:nocodb/nocodb

NixOS

To use NocoDB as a NixOS module, a flake.nix would be as follows:

{
  description = "Bane's NixOS configuration";

  inputs = {
    nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
    nocodb.url = "github:nocodb/nocodb";
  };

  outputs = inputs@{ nixpkgs, nocodb, ... }: {
    nixosConfigurations = {
      hostname = nixpkgs.lib.nixosSystem {
        system = "x86_64-linux";
        modules = [
          ./configuration.nix
          nocodb.nixosModules.nocodb

          {
            services.nocodb.enable = true;
          }
        ];
      };
    };
  };
}

Auto-upstall

Auto-upstall is a single command that sets up NocoDB on a server for production usage. Behind the scenes it auto-generates docker-compose for you.

bash <(curl -sSL http://install.nocodb.com/noco.sh) <(mktemp)

Auto-upstall does the following: 🕊

• 🐳 Automatically installs all pre-requisites like docker, docker-compose
• 🚀 Automatically installs NocoDB with PostgreSQL, Redis, Minio, Traefik gateway using Docker Compose. 🐘 🗄️ 🌐
• 🔄 Automatically upgrades NocoDB to the latest version when you run the command again.
• 🔒 Automatically setups SSL and also renews it. Needs a domain or subdomain as input while installation.

install.nocodb.com/noco.sh script can be found here in our github

Other Methods

Binaries are only for quick testing locally.

When running locally access nocodb by visiting: http://localhost:8080/dashboard

For more installation methods, please refer to our docs

Screenshots

Features

Rich Spreadsheet Interface

• ⚡  Basic Operations: Create, Read, Update and Delete Tables, Columns, and Rows
• ⚡  Fields Operations: Sort, Filter, Group, Hide / Unhide Columns
• ⚡  Multiple Views Types: Grid (By default), Gallery, Form, Kanban and Calendar View
• ⚡  View Permissions Types: Collaborative Views, & Locked Views
• ⚡  Share Bases / Views: either Public or Private (with Password Protected)
• ⚡  Variant Cell Types: ID, Links, Lookup, Rollup, SingleLineText, Attachment, Currency, Formula, User, etc
• ⚡  Access Control with Roles: Fine-grained Access Control at different levels
• ⚡  and more ...

App Store for Workflow Automations

We provide different integrations in three main categories. See App Store for details.

• ⚡  Chat: Slack, Discord, Mattermost, and etc
• ⚡  Email: AWS SES, SMTP, MailerSend, and etc
• ⚡  Storage: AWS S3, Google Cloud Storage, Minio, and etc

Programmatic Access

We provide the following ways to let users programmatically invoke actions. You can use a token (either JWT or Social Auth) to sign your requests for authorization to NocoDB.

• ⚡  REST APIs
• ⚡  NocoDB SDK

Contributing

Please refer to Contribution Guide.

Why are we building this?

Most internet businesses equip themselves with either spreadsheet or a database to solve their business needs. Spreadsheets are used by Billion+ humans collaboratively every single day. However, we are way off working at similar speeds on databases which are way more powerful tools when it comes to computing. Attempts to solve this with SaaS offerings have meant horrible access controls, vendor lock-in, data lock-in, abrupt price changes & most importantly a glass ceiling on what's possible in the future.

Our Mission

ur mission is to provide the most powerful no-code interface for databases, accessible to every internet business across the world. By making this capability broadly available under a fair and sustainable model, we aim to democratise access to powerful computing tools and enable a billion-plus people to develop radical tinkering and building abilities on the internet.

License

This project is licensed under Sustainable Use License.

Contributors

Thank you for your contributions! We appreciate all the contributions from the community.

Instalação customizada NocoDB

LInk: https://nocodb.com/docs/self-hosting/installation/custom-infrastructure

Custom Infrastructure

Use this page for NocoDB deployments that the single-server installation wizard does not cover. These include managed databases, custom SSL certificates, private CAs, your own reverse proxy, multi-replica setups and Kubernetes.

Before you begin

NocoDB works with all actively maintained PostgreSQL releases (12 and later). Use the version that your managed provider offers. We recommend a current major version.

When to use this page

Use this page if one of these is true:

Option A: Clone the repo and run the wizard interactively

git clone https://github.com/nocodb/nocodb.gitcd nocodb/docker-compose./setup.sh

setup.sh runs the same installation wizard as the Single-server install one-liner. It writes its output into the current working directory. Use this option to edit the generated files before you start the stack.

Option B: Copy a pre-built example

The docker-compose/examples/ directory contains a set of selected configurations.

To start quickly with an example:

git clone --depth 1 https://github.com/nocodb/nocodb.git cp -r nocodb/docker-compose/examples/managed-postgres ./my-deploymentcd my-deployment# Edit docker-compose.yml, docker.env, and nocodb/db.json: replace placeholdersdocker compose up -d

Configuring SSL for an external Postgres with a private CA

SSL for an external Postgres with a private CA is the most complex external database setup. NocoDB reads its database connection from nocodb/db.json (knex format). In this file, you can put a CA certificate inline:

{  "client": "pg",  "connection": {    "host": "your-private-db-host.internal",    "port": "5432",    "user": "nocodb",    "password": "your-password",    "database": "nocodb",    "ssl": {      "rejectUnauthorized": true,      "ca": "-----BEGIN CERTIFICATE-----\nMIID...\n-----END CERTIFICATE-----"    }  }}

The CA must be one string, with newlines escaped as \n. The postgres-private-ca example shows the full layout, with a Traefik proxy.

To change a multi-line PEM into the single-line JSON form, run:

awk 'NF {sub(/\r/, ""); printf "%s\\n", $0}' your-ca.pem

Multi-replica / scaling

NocoDB scales horizontally when you configure Redis. Redis is necessary for distributed coordination:

# In docker-compose.ymlnocodb:  deploy:    mode: replicated    replicas: 3

For more than a few replicas, run NocoDB in Kubernetes. Translate one of the examples into a Deployment + Service + Ingress. Point the same env vars at managed Postgres and Redis.

Bringing your own reverse proxy

The managed-postgres and external-postgres-and-redis examples expose NocoDB on host port 8080, without Traefik.

Related

Last updated on October 3, 2026