@nocobase/app-skills 0.1.0-beta.38 → 0.1.0-beta.39

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nocobase/app-skills",
3
- "version": "0.1.0-beta.38",
3
+ "version": "0.1.0-beta.39",
4
4
  "description": "Agent Skills for developing, upgrading and deploying NocoBase applications.",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -47,6 +47,7 @@ NocoBase packages may publish Skills under `.agents/skills/`. Current applicatio
47
47
  | Roles, permissions, per-user or per-record access | `@nocobase/app-plugin-authorization` |
48
48
  | Sign-in, registration, sessions | `@nocobase/app-plugin-authentication` |
49
49
  | File upload and metadata through Repository | `@nocobase/app-plugin-file` |
50
+ | File storage, disk configuration, or custom drivers | `@nocobase/drive` |
50
51
  | Translated text and language switching | `@nocobase/app-plugin-i18n` |
51
52
  | User administration and application-owned role assignment | `@nocobase/app-plugin-users` |
52
53
  | Reading or writing data, schema changes, migrations | `@nocobase/db` |
@@ -226,6 +227,8 @@ Authentication diagnostics use the application `auth` logger unless an explicit
226
227
 
227
228
  ## Storage
228
229
 
230
+ For file storage configuration and custom driver factories in `drive.disks`, read `.agents/skills/nocobase-drive/SKILL.md`, supplied by the installed `@nocobase/drive` package. Keep the application's shared Drive provider and token when adding a custom disk. [File storage](references/app-structure.md#file-storage) identifies the application configuration entry point.
231
+
229
232
  Standalone source and compiled entries share the deployment directory's storage; `APP_STORAGE_DIR` selects another storage directory, and explicit storage paths take precedence over it. Embedded applications use Host-provided paths. Expanded releases live at `appRevisionsDir/<appId>/<sha256>` and restart recovery requires their installed metadata. Build archives use `storage/exports/dist.tar.gz`.
230
233
 
231
234
  ## Process UI delivery gate
@@ -43,6 +43,10 @@ A feature with a page and an API touches five places: a migration for the table,
43
43
 
44
44
  Editable module defaults live in `server/config/` and are collected by `defaultAppConfigs` in its `index.ts`; `server/config.ts` loads the configuration file. Each section declares the environment variables that set it in `env` of its `defineAppConfig`, with a `description` and, where it applies, `secret`, `required`, `generate` or `firstStartOnly` in the helper's second argument; `pnpm nocobase config env` lists them all, `pnpm nocobase config variables` describes each, and `pnpm build` writes that description to `dist/variables.json` for whoever deploys the build. `server/config/database.ts` maps `DB_*` onto the main connection and `server/config/users.ts` maps `INITIAL_ADMIN_*` onto the initial administrator. `config.yml` is read as written: a `${NAME}` in it is not expanded. [Services and jobs](services-and-jobs.md#application-code-configuration) shows how a module declares and reads its configuration.
45
45
 
46
+ ### File storage
47
+
48
+ Configure storage in `server/config/drive.ts`, with serializable overrides in `config.yml`. Keep the default `DriveProvider` and resolve `driveManagerToken` from `@nocobase/app-server/drive`; File Repository uses the same manager. Read `.agents/skills/nocobase-drive/SKILL.md` for the `fs`, `s3`, and `oss` configuration guides, custom driver factories, URL behavior, and release artifact limitations. That Skill ships with `@nocobase/drive` and is synchronized from the installed package.
49
+
46
50
  ## The rest is framework structure
47
51
 
48
52
  `client/routing/`, `client/layouts/`, `client/theme/`, the server entry points, the `package.json` scripts that call `nocobase`, and the tsconfigs are the scaffolding the template provides. It is still this application's own source — it shipped to the user and they may change it — but it is the part the template evolves, so an edit there is what a future upgrade has to reconcile. [Customizing the shell](frontend/references/shell.md) lists the shell behaviors to keep.