### NocoDB Self-Hosted Setup Links

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/getting-started/index.mdx

Provides links to essential documentation for setting up NocoDB in a self-hosted environment, including installation, environment variables, and upgrading.

```markdown
- [Installation](/docs/self-hosting/installation/auto-upstall)
- [Environment Variables](/docs/self-hosting/environment-variables)
- [Upgrading](/docs/self-hosting/upgrading)
```

--------------------------------

### NocoDB Auto-Upstall Installation Script

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/auto-upstall.mdx

This bash script automates the installation of NocoDB, including prerequisites like Docker and PostgreSQL, and configures SSL and Traefik. It simplifies the setup process to under 2 minutes.

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

--------------------------------

### Cloudron Installation Guide

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/other-installations.mdx

Steps to install NocoDB on Cloudron, including searching for the app, installing, configuring, and launching it from the dashboard.

```markdown
1. Log in to your Cloudron dashboard.
2. Navigate to the App Store.
3. Search for NocoDB
4. Click on the NocoDB app, then click "Install".
5. Configure NocoDB settings as needed.
6. Once installed, go to "My Apps" and launch NocoDB.
```

--------------------------------

### NocoDB Relationships with Links

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/getting-started/index.mdx

Explains the concept of using Links in NocoDB to establish relationships between different tables, providing an example of linking tasks to projects.

```markdown
One of NocoDB's powerful features is the ability to establish relationships between tables using [Links](/docs/product-docs/fields/field-types/links-based/links). Links enable you to connect related data across tables. For example, you can link "Tasks" to a specific "Project" by creating a Link field in the "Projects" table that points to the "Tasks" table.
```

--------------------------------

### Start NocoDB Service

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/home-brew.mdx

Starts the NocoDB service after installation.

```bash
nocodb
```

--------------------------------

### Install NocoDB Dependencies

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/engineering/development-setup.mdx

Installs all project dependencies, including the SDK build, using the pnpm bootstrap command.

```bash
pnpm bootstrap
```

--------------------------------

### NocoDB Workspace and Base Creation

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/getting-started/index.mdx

Explains how to create new workspaces and bases in NocoDB after signing up, and how to import existing bases from Airtable.

```markdown
Your new workspace is now ready, and you can start building your base within it.

Building a base in NocoDB is where you define the structure of your database, create tables to store your data, add fields to those tables, and establish relationships between tables using Links. This relational approach helps you organize and manage your data effectively, making it easier to work with complex datasets and build powerful applications. Add a [new Base](/docs/product-docs/bases/create-base). Alternatively, you can also [import existing base from Airtable](/docs/product-docs/bases/import-base-from-airtable) as a NocoDB base in minutes.
```

--------------------------------

### Install Dependencies and Configure Environment

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/engineering/unit-testing.mdx

Installs project dependencies using pnpm and guides on setting up the environment variables for testing.

```bash
pnpm --filter=-nocodb install

# add a .env file
cp tests/unit/.env.sample tests/unit/.env

# open .env file
open tests/unit/.env
```

--------------------------------

### CapRover Deployment Guide

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/other-installations.mdx

Instructions for deploying NocoDB on CapRover, covering accessing the one-click apps, searching for NocoDB, configuring, and deploying the application.

```markdown
1. Log in to your CapRover dashboard.
2. Go to "Apps" and click on "One-Click Apps/Databases".
3. Search for NocoDB and click on it.
4. Click on NocoDB to start the configuration process.
5. Configure NocoDB settings as needed and click "Deploy".
6. Once deployed, you can access NocoDB from the provided URL.
```

--------------------------------

### NocoDB SaaS Account Signup

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/getting-started/index.mdx

Outlines the steps for signing up for a NocoDB account on their cloud-hosted (SaaS) platform, including using Google or email verification.

```markdown
1. Visit the [NocoDB website](https://www.nocodb.com).
2. Click on the "Start For Free" button located in the top right corner.
3. `Sign Up` using Google account. Alternatively, you can also sign up using your email address.
4. Check your email for a verification link and follow the instructions to verify your account.
```

--------------------------------

### Start NocoDB Frontend

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/engineering/development-setup.mdx

Starts the NocoDB frontend development server, which runs on port 3000. Changes are reflected automatically.

```bash
pnpm start:frontend
```

--------------------------------

### Full Import Example

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/scripts/api-reference/script-steps.mdx

A comprehensive example demonstrating the use of script steps throughout an import process, including starting, validating, importing, and completing stages with appropriate details and colors.

```javascript
// Step 1: Start import
script.step({
  title: 'Starting Import',
  description: 'Preparing to import customer data',
  color: 'blue',
  icon: 'database'
});

const sourceTable = await input.tableAsync('Which table has your customer data?');
const targetTable = await input.tableAsync('Which table should we import to?');

// Step 2: Validate data
script.step({
  title: 'Checking Your Data',
  description: 'Making sure the data will import correctly',
  color: 'yellow',
  icon: 'checkCircle'
});

const sourceRecords = await sourceTable.selectRecordsAsync();
if (sourceRecords.length === 0) {
  output.text('No records found to import!');
  return;
}

// Step 3: Import records
script.step({
  title: 'Importing Records',
  description: `Moving ${sourceRecords.length} customer records`,
  color: 'purple',
  icon: 'sync'
});

const newRecords = sourceRecords.map(record => ({
  'Customer Name': record.getCellValue('Name'),
  'Email': record.getCellValue('Email'),
  'Import Date': new Date()
}));

await targetTable.createRecordsAsync(newRecords);

// Step 4: Finish
script.step({
  title: 'Import Complete',
  description: `Successfully imported ${newRecords.length} customers`,
  color: 'green',
  icon: 'checkCircle'
});

script.clear();
output.text('✅ Done! Imported ' + newRecords.length + ' customer records.');
```

--------------------------------

### Start NocoDB Backend

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/engineering/development-setup.mdx

Starts the NocoDB backend development server, which runs on port 8080. Changes are reflected automatically.

```bash
pnpm start:backend
```

--------------------------------

### PostgreSQL Configuration for NocoDB

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/nix.mdx

Configures PostgreSQL for NocoDB, including enabling the service, creating a database and user, and setting authentication methods. This is recommended for production environments.

```nix
services.nocodb.environments = {
    DB_URL="postgres:///nocodb?host=/run/postgresql";
  };

  services.postgresql = {
    enable = true;

    ensureDatabases = [ "nocodb" ];
    ensureUsers = [{
      name = "nocodb";
      ensureDBOwnership = true;
    }];

    package = with pkgs; postgresql_15;
    authentication = lib.mkForce ''
        #type database DBuser  origin-address auth-method
        # unix socket
        local all      all                    trust
        # ipv4
        host  all      all     127.0.0.1/32   trust
        # ipv6
        host  all      all     ::1/128        trust
    '';

    settings.log_timezone = config.time.timeZone;
  };
```

--------------------------------

### NocoDB Base Operations API Examples

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/scripts/examples/api-ref-manual-examples.mdx

Examples for performing base operations in NocoDB, including getting all tables, checking for a specific table, and working with collaborators.

```APIDOC
Getting All Tables:
  Description: Retrieves a list of all tables within the NocoDB project.
  Endpoint: GET /api/v1/tables
  Parameters: None
  Returns: Array of table objects.

Checking for a Specific Table:
  Description: Checks if a specific table exists in the NocoDB project.
  Endpoint: GET /api/v1/tables/{tableId}
  Parameters:
    - tableId: The ID of the table to check.
  Returns: Table object if found, or 404 if not.

Working with Collaborators:
  Description: Examples related to managing and querying collaborators within NocoDB.
  Endpoint: GET /api/v1/collaborators
  Parameters: None
  Returns: Array of collaborator objects.
```

--------------------------------

### Railway Deployment Guide

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/other-installations.mdx

Steps to deploy NocoDB using Railway templates, including finding the NocoDB template, deploying, and configuring settings.

```markdown
1. Go to Railway Templates.
2. Search for "NocoDB" in the templates list.
3. Click on the NocoDB template, then click "Deploy".
4. Configure your NocoDB settings as needed.
5. Railway will automatically deploy your NocoDB instance.
```

--------------------------------

### Install Nix on Other Systems

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/nix.mdx

Installs the Nix package manager on GNU/Linux distributions and macOS using the Determinate Systems installer script. This is a prerequisite for running NocoDB with Nix if Nix is not already installed.

```bash
curl --proto '=https' --tlsv1.2 -sSf -L https://install.determinate.systems/nix | sh -s -- install
```

--------------------------------

### Start NocoDB with Docker Compose

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/docker-compose.mdx

Starts NocoDB and its PostgreSQL database in detached mode using Docker Compose.

```bash
docker-compose up -d
```

--------------------------------

### Run NocoDB using Nix

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/nix.mdx

Executes NocoDB directly from its GitHub repository using the Nix package manager. This command is used after Nix has been installed on the system.

```bash
nix run github:nocodb/nocodb
```

--------------------------------

### NocoDB Table Creation and Data Import

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/getting-started/index.mdx

Details the process of creating tables within a NocoDB base and importing data from CSV, Excel, or JSON files.

```markdown
Tables are where you store your data like a spreadsheet grid, with data arranged in rows & columns. Once the base is created, you can start [adding new tables](/docs/product-docs/tables/create-table) to it. You can also [import existing structure data from a CSV, Excel, or JSON file](/docs/product-docs/tables/create-table-via-import) to populate your tables.
```

--------------------------------

### NocoDB Record Addition and Import

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/getting-started/index.mdx

Details how to add records (data entries) to NocoDB tables, either manually or by importing data from CSV files.

```markdown
Once you have created tables and defined the necessary fields, it's time to start adding records to your base tables. Records are individual entries or rows within your tables, and they contain the actual data you want to store and manage. You can [add records manually](/docs/product-docs/records/create-record) or [upload existing data sets from CSV](/docs/product-docs/tables/import-data-into-existing-table) files.
```

--------------------------------

### NocoDB Field Management

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/getting-started/index.mdx

Describes how to define and manage fields within NocoDB tables, including using the multi-fields editor for bulk operations.

```markdown
Within each table, [define the fields](/docs/product-docs/fields) that will hold your data. Fields are columnar data containers that hold a specific type of data. Fields can represent various types of information, such as text, numbers, dates, and more. You can find complete list of supported field types [here](/docs/product-docs/fields).

Use multi-fields editor to manage fields in bulk quickly - add fields, edit them, reorder, change visibility, reconfigure - all from one single window. [Read more](/docs/product-docs/fields/multi-fields-editor).
```

--------------------------------

### NocoDB Table & Records API Examples

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/scripts/examples/api-ref-manual-examples.mdx

Examples for creating, updating, querying, filtering, and bulk processing records in NocoDB tables.

```APIDOC
Creating and Updating Records:
  Description: Demonstrates how to create new records and update existing ones in a table.
  Endpoint: POST /api/v1/tables/{tableId}/records
  Endpoint: PUT /api/v1/tables/{tableId}/records/{recordId}
  Parameters:
    - tableId: The ID of the table.
    - recordId: The ID of the record to update.
    - body: JSON object containing record data.
  Returns: Created or updated record object.

Querying and Filtering Records:
  Description: Shows how to query records with various filtering and sorting options.
  Endpoint: GET /api/v1/tables/{tableId}/records
  Parameters:
    - tableId: The ID of the table.
    - query: Filter parameters (e.g., 'filterByFormula', 'sort').
  Returns: Array of matching record objects.

Bulk Processing with Pagination:
  Description: Handles bulk operations on records, including pagination for large datasets.
  Endpoint: POST /api/v1/tables/{tableId}/bulk-process
  Parameters:
    - tableId: The ID of the table.
    - body: JSON object with bulk processing instructions.
    - limit: Number of records per page.
    - offset: Starting offset for pagination.
  Returns: Bulk processing results with pagination info.
```

--------------------------------

### NocoDB Cursor API Examples

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/scripts/examples/api-ref-manual-examples.mdx

Examples for interacting with the cursor in NocoDB, including checking context and performing bulk updates.

```APIDOC
Checking the Context:
  Description: Retrieves information about the current context or session.
  Endpoint: GET /api/v1/context
  Parameters: None
  Returns: Context details object.

Bulk Update Script:
  Description: Executes a script for bulk updating records.
  Endpoint: POST /api/v1/bulk-update
  Parameters:
    - body: JSON object containing update instructions.
  Returns: Status of the bulk update operation.
```

--------------------------------

### Single Sign-On (SSO) Configuration Reference

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/cloud-enterprise-edition/admin-panel.mdx

Provides a reference to the SSO configuration section within the Admin Panel and links to detailed setup instructions in the SSO documentation.

```English
SSO Configuration:
Access the **Single Sign-On (SSO)** section for centralized authentication setup.
Refer to: /docs/product-docs/account-settings/authentication#single-sign-on-sso
```

--------------------------------

### NixOS Module Configuration for NocoDB

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/nix.mdx

This Nix flake configuration enables the NocoDB NixOS module, setting up NocoDB and its systemd service. It assumes a basic NixOS configuration structure.

```nix
{ 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

            {
              # Enable NocoDB
              services.nocodb.enable = true;
            }
          ];
        };
      };
    };
}
```

--------------------------------

### NocoDB Fetch & External APIs Examples

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/scripts/examples/api-ref-manual-examples.mdx

Examples for fetching data from public APIs, sending data to webhooks, integrating with Google Sheets, and handling different data formats.

```APIDOC
Fetching Data from a Public API:
  Description: Retrieves data from an external public API.
  Endpoint: POST /api/v1/fetch/public
  Parameters:
    - url: The URL of the public API.
    - params: Query parameters for the request.
  Returns: Data from the public API.

Sending Data to a Webhook:
  Description: Sends data to a specified webhook URL.
  Endpoint: POST /api/v1/fetch/webhook
  Parameters:
    - url: The webhook URL.
    - data: The data payload to send.
  Returns: Status of the webhook delivery.

Integrating with Google Sheets API:
  Description: Examples for interacting with the Google Sheets API.
  Endpoint: POST /api/v1/fetch/google-sheets
  Parameters:
    - sheetId: The ID of the Google Sheet.
    - range: The range within the sheet.
    - data: Data to write to the sheet.
  Returns: Status of the Google Sheets operation.

JSON Data:
  Description: Handling JSON data for requests and responses.
  Endpoint: N/A (Content-Type: application/json)
  Usage: Send JSON payloads in request bodies or expect JSON responses.

Form Data:
  Description: Handling form-encoded data (e.g., from HTML forms).
  Endpoint: N/A (Content-Type: application/x-www-form-urlencoded)
  Usage: Send data as key-value pairs in the request body.
```

--------------------------------

### NocoDB Output API Examples

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/scripts/examples/api-ref-manual-examples.mdx

Example for creating structured reports using NocoDB output functionalities.

```APIDOC
Creating a Structured Report:
  Description: Generates a report with structured data from NocoDB.
  Endpoint: POST /api/v1/output/report
  Parameters:
    - query: Query parameters for data selection.
    - format: Desired report format (e.g., CSV, JSON).
  Returns: The generated report data.
```

--------------------------------

### Install NocoDB with Homebrew

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/home-brew.mdx

Adds the NocoDB tap and installs NocoDB using Homebrew.

```bash
brew tap nocodb/nocodb
brew install nocodb
```

--------------------------------

### NocoDB Session API Examples

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/scripts/examples/api-ref-manual-examples.mdx

Example for retrieving information about the current user's session.

```APIDOC
Getting Current User Information:
  Description: Fetches details about the currently logged-in user.
  Endpoint: GET /api/v1/user/me
  Parameters: None
  Returns: User profile object.
```

--------------------------------

### NocoDB Input API Examples

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/scripts/examples/api-ref-manual-examples.mdx

Examples for handling user input in NocoDB, including form-based data entry, file uploads, and interactive record selection.

```APIDOC
Form-Based Data Entry:
  Description: Submits data through a form interface.
  Endpoint: POST /api/v1/input/form
  Parameters:
    - body: Form data.
  Returns: Submission status.

File Upload and Processing:
  Description: Handles the upload and processing of files.
  Endpoint: POST /api/v1/input/upload
  Parameters:
    - file: The file to upload.
    - metadata: Associated metadata.
  Returns: Information about the uploaded file.

Interactive Record Selection and Update:
  Description: Allows users to select records interactively and perform updates.
  Endpoint: POST /api/v1/input/interactive-update
  Parameters:
    - recordIds: Array of record IDs to update.
    - updates: Data for updates.
  Returns: Status of the interactive update.
```

--------------------------------

### FreeBSD/FreeNAS/TrueNAS Jail Installation

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/other-installations.mdx

Reference to an external guide for installing NocoDB on FreeBSD, FreeNAS, or TrueNAS Jail environments.

```markdown
For detailed instructions on installing NocoDB on FreeBSD, FreeNAS, or TrueNAS Jail, please refer to the [guide](https://gist.github.com/Zamana/e9281d736f9e9ce5882c6f4b140a590e) provided by [C. R. Zamana.](https://github.com/Zamana)
```

--------------------------------

### Install Python Requests

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/developer-resources/rest-apis/upload-via-api.mdx

Installs the 'requests' library for Python, which is required for making HTTP requests in the Python example.

```bash
pip install requests
```

--------------------------------

### Install Ruby Gems

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/developer-resources/rest-apis/upload-via-api.mdx

Installs the 'multipart-post' and 'mime-types' gems for Ruby, which are necessary for handling file uploads and MIME types in the Ruby example.

```bash
gem install multipart-post mime-types
```

--------------------------------

### Table Operations in NocoDB Scripting

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/scripts/examples/demo/index.mdx

Examples demonstrating how to programmatically create tables and manage their structure within NocoDB.

```javascript
/*
  Working with Tables:
  Examples for creating tables and managing their structure programmatically.
  See: /docs/scripts/examples/demo/table-operations
*/
```

--------------------------------

### Making a GET Request with remoteFetchAsync

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/scripts/api-reference/fetch.mdx

A basic example of making a GET request to an external API using the remoteFetchAsync function and inspecting the response data.

```javascript
// Simple GET request
const response = await remoteFetchAsync('https://api.example.com/data');
output.text(`Response status: ${response.status}`);
output.inspect(response.data);
```

--------------------------------

### Clone NocoDB Repository

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/engineering/development-setup.mdx

Clones the NocoDB repository from GitHub and navigates into the project directory.

```bash
git clone https://github.com/nocodb/nocodb
cd nocodb
```

--------------------------------

### Example Test Case: Get Table List

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/engineering/unit-testing.mdx

An example of a unit test that fetches a list of tables using supertest and asserts the response using chai.

```typescript
it('Get table list', async function () {
  const response = await request(context.app)
    .get(`/api/v1/db/meta/projects/${project.id}/tables`)
    .set('xc-auth', context.token)
    .send({})
    .expect(200);

  expect(response.body.list).to.be.an('array').not.empty;
});
```

--------------------------------

### Noco AI Base Creation Prompt Example - Specific

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/noco-ai/create-base.mdx

Example of a more specific prompt for tracking projects, including assigned team members, tasks, deadlines, and status updates.

```Noco AI
Track multiple projects with assigned team members, tasks, deadlines, and project status updates.
```

--------------------------------

### Run Development Server

Source: https://github.com/nocodb/noco-docs-v2/blob/main/README.md

Commands to start the Next.js development server using npm, pnpm, or yarn.

```bash
npm run dev
# or
pnpm dev
# or
yarn dev
```

--------------------------------

### Docker: Example Upgrade Process

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/upgrading.mdx

A detailed example demonstrating the process of upgrading a NocoDB Docker container, including stopping and removing the old container and image, then running the latest image.

```bash
# Previous docker run
#
terminal % docker run -d --name myNocoDB \
-v "$(pwd)"/nocodb:/usr/app/data/ \
-p 8080:8080 \
-e NC_DB="pg://host.docker.internal:5432?u=postgres&p=password&d=d1" \
-e NC_AUTH_JWT_SECRET="569a1821-0a93-45e8-87ab-eb857f20a010" \
nocodb/nocodb:0.111.0
Unable to find image 'nocodb/nocodb:0.111.0' locally
0.111.0: Pulling from nocodb/nocodb
ad3fa0ea069c: Pull complete 
e43b9156e769: Pull complete 
c1bee0da1504: Pull complete 
adf78ab024d9: Pull complete 
cd8000d2c16a: Pull complete 
Digest: sha256:93b6e1ba2c0b90a26b205f9c7d44053aa6d8fa037eff9eb4155ca017f6c9bed4
Status: Downloaded newer image for nocodb/nocodb:0.111.0
afdc8edd1005c93e1df8f90d02e46430ea7b5c5610a2bf9ba105238d6c4d927b


# Find, stop and delete NocoDB docker container
#
terminal % docker ps
CONTAINER ID   IMAGE                   COMMAND                  CREATED          STATUS                 PORTS                    NAMES
afdc8edd1005   nocodb/nocodb:0.111.0   "/usr/bin/dumb-init …"   18 seconds ago   Up 18 seconds          0.0.0.0:8080->8080/tcp   myNocoDB
0202041b3607   postgres:14.7           "docker-entrypoint.s…"   2 days ago       Up 8 hours (healthy)   0.0.0.0:5432->5432/tcp   scripts_pg147_1

terminal % docker stop afdc8edd1005
afdc8edd1005

terminal % docker rm afdc8edd1005
afdc8edd1005


# Find and remove NocoDB docker image
#
terminal % docker images
REPOSITORY      TAG       IMAGE ID       CREATED        SIZE
nocodb/nocodb   0.111.0   34609411e87c   5 weeks ago    132MB
mysql           8.0       6a0560a40914   7 weeks ago    599MB
postgres        14.7      2075a95c7b3b   4 months ago   358MB

terminal % docker rmi 34609411e87c
Untagged: nocodb/nocodb:0.111.0
Untagged: nocodb/nocodb@sha256:93b6e1ba2c0b90a26b205f9c7d44053aa6d8fa037eff9eb4155ca017f6c9bed4
Deleted: sha256:3bfxxxx38e682742cbxxxx535b3503af45e931fb9bd15f46eca7d33cf4c54d72
Deleted: sha256:952152b5da42ae057c6688a04xxxx72e1a2f91825956f5c7e35f91d5b285d4d8
Deleted: sha256:3155197577xxxx673675ed1bce761714a24d7803f70a905740f7d4c248cxxxxx


# Pull & run the latest NocoDB image with same environment variables as before
#
terminal % docker run -d --name myNocoDB \
-v "$(pwd)"/nocodb:/usr/app/data/ \
-p 8080:8080 \
-e NC_DB="pg://host.docker.internal:5432?u=postgres&p=password&d=d1" \
-e NC_AUTH_JWT_SECRET="569a1821-0a93-45e8-87ab-eb857f20a010" \
nocodb/nocodb:latest
Unable to find image 'nocodb/nocodb:latest' locally
latest: Pulling from nocodb/nocodb
ad3fa0ea069c: Pull complete 
e43b9156e769: Pull complete 
c1bee0da1504: Pull complete 
adf78ab024d9: Pull complete 
28ce4fc94e48: Pull complete 
Digest: sha256:5c6df5ff0eb1278e1dbfe684af630a743ca73dfec8c30cab3bae9c1d0d640287
Status: Downloaded newer image for nocodb/nocodb:latest
ae793a04b75f2f3ee78abbaef09891396a884ec83320151a266326195649a058
```

--------------------------------

### Deploy on Elestio

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/other-installations.mdx

Link to deploy NocoDB on Elestio, a platform for deploying open-source applications.

```markdown
[![Deploy on Elestio](/img/v2/installations/deploy-to-elestio-btn.png)](https://elest.io/open-source/nocodb)
```

--------------------------------

### NocoDB Secrets Management with environmentFile

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/self-hosting/installation/nix.mdx

Configures NocoDB to use an environment file for secrets, such as the JWT secret. This is a recommended practice to avoid committing sensitive data directly into the NixOS configuration.

```nix
services.nocodb.environmentFile = "/var/lib/secrets/nocodb.env"
```

--------------------------------

### Noco AI Base Creation Prompt Example

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/noco-ai/create-base.mdx

Example of a natural language prompt to generate a hiring process management base, including candidate applications, interview scheduling, and tracking hiring outcomes.

```Noco AI
Streamline the hiring process by managing candidate applications, scheduling interviews, and tracking hiring outcomes.
```

--------------------------------

### Additional Resources for NocoDB Scripts

Source: https://github.com/nocodb/noco-docs-v2/blob/main/content/docs/automation/scripts/actions-on-script.mdx

Provides links to further documentation and examples for NocoDB scripts, including general script documentation, examples for find and replace functionality, and the script API reference.

```English
The following resources can help you get started with NocoDB scripts:
- [Script Documentation](/docs/scripts)
- [Script Examples](/docs/scripts/examples/find-and-replace)
- [Script API Reference](/docs/scripts/api-reference/base)
```