Skip to content

Budibase #2404

Open
Open

Description

@MickLesk

Name of the Script

Budibase

Script Type

CT (LXC Container)

Script path

No response

Where does it run?

Proxmox VE host

Does this script support arm64?

arm64 not tested

📋 Script Details

Budibase is a low-code platform for building internal tools: forms, portals, admin panels and approval apps on top of its built-in database or external sources such as PostgreSQL, MySQL, REST APIs and Google Sheets, plus automations triggered by events, schedules or webhooks. This script builds the app server and worker from source and runs them with CouchDB, Clouseau, SQS, Redis, Silo object storage and nginx, without Docker.

Activity

  1. github-actions commented on Oct 9, 2026

    @github-actions
    Contributor

    The Budibase script is ready for testing. Run it in the Proxmox VE shell (or on an Incus host) to create a container:

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/DevScripts/main/ct/budibase.sh)"
    

    There is no default account. Open http:// right after the install and create the admin account on the setup page: until then anyone who reaches port 80 can claim it.
    Without a license key Budibase runs its free self-hosted plan: one workspace, unlimited users and rows, no user groups and no custom AI providers. The paid features live in the source-available @budibase/pro package (Business Source License) and are unlocked with a key from account.budibase.app.
    Budibase itself is GPLv3. Its internal tables are queried through SQS, a proprietary binary by The Neighbourhoodie Software that Budibase ships in every release and licenses for your own internal business use only (SQS_LICENSE in the repository).
    The official image also bundles a LiteLLM proxy for AI agents and custom AI providers, which need a paid plan. It is not installed here; point LITELLM_URL and LITELLM_MASTER_KEY in /opt/budibase_data/.env at your own LiteLLM and run systemctl restart budibase-server to use one.
    Install and every update download about 4 GB of npm packages and compile Budibase from source: expect 15 to 30 minutes, mostly downloading, up to about 3.3 GB of RAM and 9 GB of disk. The running stack uses about 2.5 GB of RAM.
    Back up /opt/budibase_data as a whole: it holds the CouchDB databases, the object storage with uploads and app assets, the search and SQS indexes, and the .env whose JWT_SECRET, API_ENCRYPTION_KEY and ENCRYPTION_KEY sign sessions and encrypt API keys and stored secrets.
    Services: nginx on port 80 in front of budibase-server (4001) and budibase-worker (4002), plus couchdb, budibase-clouseau (search), budibase-sqs, budibase-silo (S3 object storage, a maintained MinIO fork) and redis-server.

    Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

    Discord testing thread: https://discord.com/channels/1302816934508630047/1558017218497880090

  2. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    📊 Install telemetry for budibase

    Runs reported by the DevScripts version of this script since this issue was opened (2026-10-09).

    Installs ✅ Successful ❌ Failed ⏹️ Aborted ❔ No result Success rate
    17 14 1 2 0 82.4%

    Last run: 10.11.2026 at 20:00 UTC (2 days 22 hours ago) · success

    Last success: 2026-11-10 20:16 UTC · Last failure: 2026-10-12 23:34 UTC · Avg. install time: 11 min

    Failures by cause

    Count Exit code Error Last seen
    1 1 General error yarn install --frozen-lockfile
    error AggregateError [ETIMEDOUT]:
    2026-10-12 23:34 UTC

    Open in the telemetry dashboard · updated hourly · last refresh 2026-11-13 18:18 UTC

  3. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    ⚠️ Marked as stale. budibase since this issue was opened:

    • only 1 successful install(s) in the last 7 days (15 needed), 17 install(s) in total

    This issue will be closed due to lack of testing 7 days after this label, unless it recovers first: the label is removed again automatically once the script has 15 successful installs in 7 days (or more than 100 installs in total) and, past 50 installs, a success rate of at least 75% (aborted and no-result runs count as failed). Maintainers can add keep-open to skip this check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions