Go to file
2024-02-08 11:37:44 +08:00
.github Merge branch 'main' into feat/dataSource-manager 2024-02-08 11:37:44 +08:00
.vscode chore(vscode): add inspect argument for attaching to debug port (#3307) 2024-01-03 09:19:51 +08:00
benchmark perf(server): optimize performance of APIs (#3079) 2023-12-12 23:02:09 +08:00
docker feat: update docs 2024-01-13 18:36:11 +08:00
examples feat: application supervisor (#2353) 2023-08-24 17:47:45 +08:00
packages Merge branch 'main' into feat/dataSource-manager 2024-02-08 11:37:44 +08:00
storage fix: e2e with build 2024-01-08 10:29:41 +08:00
.dockerignore chore: dockerignore 2023-08-02 13:45:52 +08:00
.editorconfig
.env.e2e.example fix: e2e with build 2024-01-08 10:29:41 +08:00
.env.example refactor(logger): improve logger format (#2664) 2023-12-27 13:56:13 +08:00
.env.test.example feat(auth): support signing in with username (#2376) 2023-08-19 22:02:26 +08:00
.eslintignore test: workflow e2e (#3261) 2023-12-29 09:13:00 +08:00
.eslintrc test(e2e): add tests for client (#3144) 2023-12-13 14:14:33 +08:00
.gitignore feat: application backup and restore (#3268) 2024-01-08 18:59:56 +08:00
.gitpod.yml chore: gitpod yml 2023-02-15 14:47:02 +00:00
.prettierignore feat: new plugin manager, supports adding plugins through UI (#2430) 2023-09-12 22:39:23 +08:00
.prettierrc
CHANGELOG.md chore: update changelog 2024-02-07 20:11:22 +08:00
commitlint.config.js fix: eslint (#1759) 2023-04-25 13:12:14 +08:00
deploy-docs-cn.sh feat: update docs 2023-06-20 18:05:06 +08:00
deploy-docs.sh feat: update docs 2023-06-20 18:05:06 +08:00
docker-compose.yml feat: database view collection (#1587) 2023-04-01 21:56:01 +08:00
Dockerfile fix: build bug 2024-02-07 08:12:50 +08:00
lerna.json chore(versions): 😊 publish v0.19.0-alpha.6 2024-02-07 20:11:19 +08:00
LICENSE-AGPL feat: change license (#1350) 2023-01-11 11:58:47 +08:00
LICENSE-APACHE-2.0 feat: change license (#1350) 2023-01-11 11:58:47 +08:00
package.json fix: remove tree-kill package to core/cli (#3429) 2024-01-24 16:05:29 +08:00
playwright.config.ts refactor: establish a sound testing system (#3179) 2023-12-21 20:39:11 +08:00
README.md Update README.md 2024-01-12 09:59:38 +08:00
README.zh-CN.md feat: update readme.md 2024-01-08 19:37:23 +08:00
release.sh fix: update release.sh 2023-11-01 09:52:19 +08:00
SECURITY.md Update SECURITY.md 2023-11-29 15:46:06 +08:00
tsconfig.json refactor: establish a sound testing system (#3179) 2023-12-21 20:39:11 +08:00
tsconfig.server.json
vitest.config.mts refactor: establish a sound testing system (#3179) 2023-12-21 20:39:11 +08:00
yarn.lock fix: bug 2024-02-06 10:41:13 +08:00

English | 中文

NocoBase

Note: 📌

NocoBase is in early stage of development and is subject to frequent changes, please use caution in production environments.

Recent major updates

What is NocoBase

NocoBase is a scalability-first, open-source no-code development platform.
Instead of investing years of time and millions of dollars in research and development, deploy NocoBase in a few minutes and you'll have a private, controllable, and extremely scalable no-code development platform!

Homepage:
https://www.nocobase.com/

Online Demo:
https://demo.nocobase.com/new

Documents:
https://docs.nocobase.com/

Contact Us:
hello@nocobase.com

Distinctive features

1. Model-driven, separate "user interface" from "data structure"

Most form-, table-, or process-driven no-code products create data structures directly in the user interface, such as Airtable, where adding a new column to a table is adding a new field. This has the advantage of simplicity of use, but the disadvantage of limited functionality and flexibility to meet the needs of more complex scenarios.

NocoBase adopts the design idea of separating the data structure from the user interface, allowing you to create any number of blocks (data views) for the data collections, with different type, styles, content, and actions in each block. This balances the simplicity of no-code operation with the flexibility of native development.

model

2. What you see is what you get

NocoBase enables the development of complex and distinctive business systems, but this does not mean that complex and specialized operations are required. With a single click, configuration options are displayed on the usage interface, and administrators with system configuration privileges can directly configure the user interface in a WYSIWYG manner.

wysiwyg

3. Functions as plugins

NocoBase adopts plugin architecture, all new functions can be realized by developing and installing plugins, and expanding the functions is as easy as installing an APP on your phone.

plugins

Installation

NocoBase supports three installation methods:

  • Installing With Docker (👍Recommended)

    Suitable for no-code scenarios, no code to write. When upgrading, just download the latest image and reboot.

  • Installing from create-nocobase-app CLI

    The business code of the project is completely independent and supports low-code development.

  • Installing from Git source code

    If you want to experience the latest unreleased version, or want to participate in the contribution, you need to make changes and debug on the source code, it is recommended to choose this installation method, which requires a high level of development skills, and if the code has been updated, you can git pull the latest code.

License