Go to file
2022-07-20 15:28:13 +08:00
.github Update issue templates 2022-07-06 11:33:49 +08:00
.vscode fix(plugin-workflow): clear options when change collection (#547) 2022-06-28 18:48:16 +08:00
docker chore(versions): 😊 publish v0.7.3-alpha.1 (#657) 2022-07-20 15:28:13 +08:00
docs chore(versions): 😊 publish v0.7.3-alpha.1 (#657) 2022-07-20 15:28:13 +08:00
packages chore(versions): 😊 publish v0.7.3-alpha.1 (#657) 2022-07-20 15:28:13 +08:00
storage feat: improvements (#335) 2022-04-29 00:09:40 +08:00
.buildrc.ts feat: build, cli, devtools, sdk, docs... 2022-05-19 00:40:55 +08:00
.editorconfig Feat: client base entry of plugin workflow (#225) 2022-03-27 15:51:48 +08:00
.env.example feat: build, cli, devtools, sdk, docs... 2022-05-19 00:40:55 +08:00
.eslintignore v0.6 2021-12-06 21:23:34 +08:00
.eslintrc v0.5 2021-05-23 08:38:08 +08:00
.gitignore feat: build, cli, devtools, sdk, docs... 2022-05-19 00:40:55 +08:00
.prettierignore feat: translation 2022-05-01 11:09:22 +08:00
.prettierrc refactor: code splitting of the table component (#121) 2021-12-02 22:56:16 +08:00
.umirc.ts feat: build, cli, devtools, sdk, docs... 2022-05-19 00:40:55 +08:00
commitlint.config.js fix(root): change wrong file mode 2022-04-23 23:26:19 +08:00
docker-compose.yml docs: update installation documentation 2022-05-25 21:00:45 +08:00
jest.config.js feat: build, cli, devtools, sdk, docs... 2022-05-19 00:40:55 +08:00
jest.setup.ts feat: error handle middleware (#214) 2022-03-02 12:50:15 +08:00
lerna.json chore(versions): 😊 publish v0.7.3-alpha.1 (#657) 2022-07-20 15:28:13 +08:00
LICENSE feat(license): replace MIT license with Apache-2.0 2022-04-25 09:45:24 +08:00
package.json feat: build, cli, devtools, sdk, docs... 2022-05-19 00:40:55 +08:00
README.md Update README.md 2022-06-18 09:28:52 +08:00
README.zh-CN.md Update README.zh-CN.md 2022-06-18 09:30:29 +08:00
tsconfig.jest.json feat: build, cli, devtools, sdk, docs... 2022-05-19 00:40:55 +08:00
tsconfig.json refactor: client application (#533) 2022-06-24 21:19:57 +08:00
tsconfig.server.json feat: build, cli, devtools, sdk, docs... 2022-05-19 00:40:55 +08:00
yarn.lock feat: print action (#652) 2022-07-20 14:12:18 +08:00

English | 中文

Note: 📌

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

What is NocoBase

NocoBase is a scalability-first, open-source no-code development platform. No programming required, build your own collaboration platform, management system with NocoBase in minutes.

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

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

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

Contact Us:
hello@nocobase.com

Who is NocoBase for

NocoBase is designed for you if you have the following needs.

  • Develop an internal management system
  • Meet most of your business needs with no-code development
  • No-code development is simple enough for non-developers; flexible enough to be close to native development
  • Can be very easy to extend
  • Private deployment with full control of code and data
  • Free to use or pay for more technical support

Why NocoBase is different

1. Separate "data structure" and "user interface"

Most form-, table-, or process-driven codeless 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 takes into account the simplicity of codeless operation, but also the flexibility like native development.

2.collection-block.png

2. Integrate "system configuration" and "system use"

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 can be displayed on the usage interface, which means that administrators with system configuration rights can configure the user interface directly with WYSIWYG operations.

2.user-root.gif

3. Everything is a plugin

NocoBase adopts plugin architecture, all new features can be implemented by developing and installing plugins. In the future, we will build a plug-in marketplace where extending functionality is as easy as installing an APP on your phone.

Click to view the full image

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.