a57c93d35b
* chore: upgrade vitest to v0.34.3 * feat: setup NocoBase * chore: preparing test env * test: add a test of rigster * refactor: rename test dir to testUtils * chore: add tests * chore: add ci for e2e * chore: fix ci * chore: avoid error in CI * chore: add some utils for test * chore: make more stable * chore: should not close server in CI * chore: add comments * chore: change output dir * fix: should use current branch to run tests * chore: should request systemSettings by api in e2e * chore: should build first in e2e CI * chore: remove key * chore: use execa to replace execSync * refactor: extract test suite * chore: add gotoPage * chore: update uid of pageSchema * chore: update collection name * chore: use faker.js to generate data * refactor: extract page config * chore: ignore for association fields in faker * chore: add testid * chore: optimize action designer * chore: associationFilter.Item designer * chore: AssiciationFilter & BlockItem * Revert "chore: AssiciationFilter & BlockItem" This reverts commit b418df650e106fd0c8e23035d2f75acf60dcafe4. * Revert "chore: associationFilter.Item designer" This reverts commit 7aa4d35c1af7f3a780b370d8b1b44aac01697be3. * Revert "chore: optimize action designer" This reverts commit ff717b972ffd64f7968d565a3a84ad617ff889e2. * chore: optimize Designer * chore: compat with older browsers * chore: use describe to avoid hooks is not run * chore: add no-floating-promises to eslint rules * chore: support argv * chore: demo * chore: better testId * chore: change .e2e.ts to .test.ts * fix(SchemaInitializer): avoid error * refactor: move e2eUtils.ts to @nocobase/test * fix: move e2eUtils to client * chore: remove uselesscode * refactor: add .env.e2e.example * chore: optimize log * refactor: use mockPage to replace gotoPage * chore: update env.e2e * chore: add APP_BASE_URL * chore: gitigore * test: add test related of menu * chore: add SOCKET_PATH in env * fix(vscode): load env when using vscode plugin |
||
---|---|---|
.dumi/theme/slots | ||
.github | ||
.vscode | ||
docker | ||
docs | ||
examples | ||
packages | ||
scripts | ||
storage | ||
.dockerignore | ||
.dumirc.ts | ||
.editorconfig | ||
.env.e2e.example | ||
.env.example | ||
.env.test.example | ||
.eslintignore | ||
.eslintrc | ||
.gitignore | ||
.gitpod.yml | ||
.prettierignore | ||
.prettierrc | ||
CHANGELOG.md | ||
commitlint.config.js | ||
deploy-docs-cn.sh | ||
deploy-docs.sh | ||
docker-compose.yml | ||
Dockerfile | ||
jest.config.js | ||
jest.setup.ts | ||
jest.setupAfterEnv.ts | ||
lerna.json | ||
LICENSE-AGPL | ||
LICENSE-APACHE-2.0 | ||
package.json | ||
playwright.config.ts | ||
README.md | ||
README.tr-TR.md | ||
README.zh-CN.md | ||
release.sh | ||
testUtils.ts | ||
tsconfig.jest.json | ||
tsconfig.json | ||
tsconfig.server.json | ||
vitest.config.ts | ||
yarn.lock |
Note: 📌
NocoBase is in early stage of development and is subject to frequent changes, please use caution in production environments.
Recent major updates
- v0.14: New plugin manager, supports adding plugins through UI - 2023/09/11
- v0.13: New application status flow - 2023/08/24
- v0.12: New plugin build tool - 2023/08/01
- v0.11: New client application, plugin and router - 2023/07/08
- v0.10: Update instructions - 2023/06/23
We are hiring
We are looking for full-time, remote product design and development colleagues to join the team. If you have a strong interest in NocoBase, please feel free to email us at hello@nocobase.com.
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 hours.
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. 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 can be displayed on the usage interface, which means that administrators with system configuration rights can configure the user interface directly with WYSIWYG operations.
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.
Business Services
If you need commercial version and commercial services, please feel free to contact us by email: hello@nocobase.com
Also by WeChat:
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.