6cfd586175
* feat(plugin-api-keys): support fetch api via api-keys * feat: full support * fix: missing parseToken in auth * feat: add created at column * feat: configure snippet * fix: remove unused code * fix: revert * chore: update deps * feat: improve role * fix: avoid create api key without not exist role * feat: improve select roles * refactor: when no X-Role is found, roles should not be randomly assigned * feat: improve code * feat: improve current role * fix: revert * fix: revert apilicent * fix: revert auth * feat: improve currentRole logic * feat: use resourcer.use instead it * refactor: remove api-keys-auth * fix: type * refactor: move jwt to authManager * refactor: remove unused code * refactor: remove protected * Revert "refactor: remove unused code" This reverts commit 8f81535ab7e9c412bdc4d4bc05abad64ff60ba3f. * feat: remove unused code * feat: improve code * fix: test error * test: update test * test: add test cases * docs: update * chore: update X-Role * fix: token's roleName not work * docs: update usage * fix: i18n Add APi key * docs: update capital * docs: update * feat: clean * Update package.json * Update roles.ts * fix: api key --------- Co-authored-by: chenos <chenlinxh@gmail.com> |
||
|---|---|---|
| .dumi | ||
| .github | ||
| .vscode | ||
| docker | ||
| docs | ||
| examples | ||
| packages | ||
| scripts | ||
| storage | ||
| .buildrc.ts | ||
| .dumirc.ts | ||
| .editorconfig | ||
| .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 | ||
| Dockerfile.acr | ||
| jest.config.js | ||
| jest.setup.ts | ||
| jest.setupAfterEnv.ts | ||
| lerna.json | ||
| LICENSE-AGPL | ||
| LICENSE-APACHE-2.0 | ||
| package.json | ||
| README.md | ||
| README.tr-TR.md | ||
| README.zh-CN.md | ||
| 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.
NocoBase v0.10 has been released, see v0.10: update instructions for details.
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.