To install NocoDB with Docker and build a no-code database app, run the official NocoDB container, connect it to SQLite or PostgreSQL, and open the dashboard through your server’s browser URL. Once deployed, NocoDB turns database tables into spreadsheet-style workspaces where you can edit records, create views, invite users, and manage data without building a custom admin panel.<\/p>
The process has five main parts:<\/p>
For a faster setup, Hostinger’s Docker template deploys NocoDB on a VPS without manually pulling the image or configuring the container from the command line.<\/p>
Before installing NocoDB with Docker, prepare a server environment, a database option, and access details for the web dashboard. These requirements make sure the container runs correctly and keeps your NocoDB data available after restarts or updates.<\/p>
You need:<\/p>
For a quick test, SQLite is enough because it stores data in the mapped NocoDB data directory. For a team workspace or production app, use PostgreSQL<\/a> because it separates the application container from the database and handles larger, multi-user workloads more reliably.<\/p> You can install NocoDB with Docker by running the official nocodb\/nocodb image as a container and exposing its web interface on port 8080. For a quick test setup, use SQLite. For a production setup or a multi-user database app, connect NocoDB to PostgreSQL or another external database.<\/p> Before starting, make sure Docker is installed on your server and that port 8080 is available.<\/p> SQLite is the simplest way to get started with NocoDB because it doesn’t require a separate database server. Run this command from the directory where you want to store NocoDB data:<\/p> This command does four things:<\/p> The volume mapping is important. Without it, your NocoDB data may be lost when the container is removed.<\/p> PostgreSQL is better for production projects because it separates the NocoDB application from the database layer. Use this setup if you plan to manage larger datasets, invite multiple users, or connect NocoDB to an existing database.<\/p> Replace the database host, username, password, database name, and JWT secret before running the command:<\/p> In this command:<\/p> Use a long, unique value for NC_AUTH_JWT_SECRET. Do not reuse the example value in a live deployment.<\/p> After the container starts, open NocoDB in your browser:<\/p> If NocoDB is running on a VPS, replace localhost with your server IP address:<\/p> From there, create your admin account and start building your no-code database interface. You can create a new base, connect an existing database, or import data into a spreadsheet-style workspace.<\/p> Use this command to confirm that the NocoDB container is active:<\/p> If the container is running, you should see nocodb\/nocodb:latest in the image column and 0.0.0.0:8080->8080\/tcp in the ports column.<\/p> If NocoDB doesn’t open in your browser, check the container logs:<\/p> The logs help identify common issues, such as port conflicts, incorrect database credentials, or failed container startup.<\/p> Hostinger’s Docker catalog<\/a> lets you deploy NocoDB without manually pulling the Docker image, configuring the container, or mapping ports through the command line. The template creates a ready-to-use NocoDB instance<\/a> on your VPS, so you can move straight to setting up your no-code database interface.<\/p> Here’s how to deploy it:<\/p> After deployment, NocoDB runs as a Docker container on your VPS. You can manage it from Hostinger’s Docker manager instead of using only terminal commands. This is useful for checking container status, viewing logs, restarting the application, or updating the container when a new version is available.<\/p> Hostinger’s template is best suited for users who want the benefits of self-hosting without having to manually complete every Docker setup step. You still control the VPS environment, database app, users, and stored data, but the initial deployment process is faster than running NocoDB from scratch.<\/p> Once NocoDB is running, connect your database or create a new base. Then, use grid, form, kanban, gallery, or calendar views to turn your data into a spreadsheet-style app for your team.<\/p> NocoDB turns a database into a spreadsheet-style app by converting database tables into visual workspaces. Instead of writing SQL queries or building a custom admin panel, you can manage records through editable rows, fields, filters, views, forms, and permissions.<\/p> After installing NocoDB, open the dashboard and follow these steps:<\/p> For example, a sales team can connect a customer database to NocoDB and manage it as a CRM. The grid view can show every lead as a spreadsheet row, the kanban view can group leads by pipeline stage, and the form view can collect new inquiries from a website.<\/p> The main benefit is that NocoDB keeps the database structure in place while making the data easier to use. Developers can still work with the underlying database, while non-technical users can update records, filter information, and collaborate through a visual interface.<\/p> NocoDB needs regular container checks, updates, backups, and access controls after installation. These tasks keep the app available for users and protect the database records behind your spreadsheet-style interface.<\/p> Start by checking whether the NocoDB container is running:<\/p> If the container is active, the output should show the nocodb\/nocodb:latest image and port 8080 mapped to your server.<\/p> If NocoDB doesn’t open in your browser, check the container logs:<\/p> The logs help identify startup errors, port conflicts, database connection issues, or missing environment variables.<\/p> Restart NocoDB when the container is running but the dashboard is not responding:<\/p> To stop and remove the container, use:<\/p> Only remove the container after confirming that your data is stored in a persistent volume or external database. The Docker volume keeps NocoDB data outside the container, so it remains available after restarts or updates.<\/p> Update NocoDB by pulling the latest Docker image and recreating the container with the same volume and environment variables:<\/p> Before updating, create a backup of your database and NocoDB data directory. This is especially important for production setups that use PostgreSQL or contain team workspaces, forms, API tokens, and permission settings.<\/p> Secure NocoDB by limiting access to the server, protecting database credentials, and assigning users only the permissions they need.<\/p> Follow these practices:<\/p> Once NocoDB is running, start with a small database workflow before adding more users, views, and automations. This helps you validate the structure of your no-code app before relying on it for production data.<\/p> First, decide what your app should manage. NocoDB works well for internal tools like CRMs, inventory trackers, project dashboards, content calendars, applicant trackers, and customer support databases. Each workflow should have a clear main table, such as customers, products, tasks, articles, applicants, or tickets.<\/p> Next, create the views your team needs. Use grid view for spreadsheet-style editing, form view for collecting new records, kanban view for pipeline stages, calendar view for date-based work, and gallery view for visual records. Keep the first setup simple, then add more fields and views when users need them.<\/p> Once the basic app structure is in place, invite team members and assign permissions. Give each user only the access they need. For example, sales reps may need permission to update leads, while managers may need access to pipeline reports and workspace settings.<\/p> Finally, connect NocoDB to the rest of your workflow. Use APIs, webhooks, or external automation tools to send data between NocoDB and your website, forms, analytics tools, or internal systems. If your app will handle business-critical data, use a production database like PostgreSQL, enable HTTPS, and schedule regular backups before expanding usage.<\/p> With Docker, NocoDB gives you a self-hosted way to turn database records into a collaborative spreadsheet-style app. With Hostinger’s Docker template, you can skip most of the manual setup and focus on building the database interface your team actually needs.<\/p>\n","protected":false},"excerpt":{"rendered":" To install NocoDB with Docker and build a no-code database app, run the official NocoDB container, connect it to SQLite […]<\/p>\nHow to install NocoDB with Docker<\/h2>
1. Run NocoDB with SQLite<\/h3>
docker run -d --name nocodb\n-v \"$(pwd)\"\/nocodb:\/usr\/app\/data\/\n-p 8080:8080\nnocodb\/nocodb:latest<\/pre>
\n
2. Run NocoDB with PostgreSQL<\/h3>
docker run -d --name nocodb\n-v \"$(pwd)\"\/nocodb:\/usr\/app\/data\/\n-p 8080:8080\n-e NC_DB=\"pg:\/\/your-database-host:5432?u=your-username&p=your-password&d=your-database-name\"\n-e NC_AUTH_JWT_SECRET=\"replace-this-with-a-secure-random-secret\"\nnocodb\/nocodb:latest<\/pre>
\n
3. Open the NocoDB dashboard<\/h3>
http:\/\/localhost:8080<\/pre>
http:\/\/your-server-ip:8080<\/pre>
4. Check whether the container is running<\/h3>
docker ps<\/pre>
docker logs nocodb<\/pre>
How to deploy NocoDB with Hostinger’s Docker template<\/h2>
\n
How to turn a database into a spreadsheet-style app with NocoDB<\/h2>
\n
How to manage NocoDB after installation<\/h2>
Check the NocoDB container status<\/h3>
docker ps<\/pre>
docker logs nocodb<\/pre>
Restart or stop the NocoDB container<\/h3>
docker restart nocodb<\/pre>
docker stop nocodb\ndocker rm nocodb<\/pre>
Update NocoDB safely<\/h3>
docker pull nocodb\/nocodb:latest<\/pre>
Secure your NocoDB deployment<\/h3>
\n
Next steps for building a no-code database app<\/h2>