harivansh-afk/betterNAS
1
1
Fork 0
mirror of https://github.com/harivansh-afk/betterNAS.git synced 2026-04-18 16:02:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

rename2

Browse source
This commit is contained in:
Harivansh Rathi 2026-04-01 02:28:45 +00:00
parent 12c53f3515
commit dc7969e579
37 changed files with 177 additions and 177 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/current-architecture.md
View file

@ -1,18 +1,18 @@
# aiNAS Architecture Boundary
# betternas Architecture Boundary
## Core Decision
aiNAS treats Nextcloud as an upstream backend, not as the place where aiNAS product logic should accumulate.
betternas treats Nextcloud as an upstream backend, not as the place where betternas product logic should accumulate.
That leads to three explicit boundaries:
1. `apps/betternas-controlplane/` is a thin shell inside Nextcloud.
2. `exapps/control-plane/` owns aiNAS business logic and internal APIs.
2. `exapps/control-plane/` owns betternas business logic and internal APIs.
3. `packages/contracts/` defines the interface between the shell app and the control plane.
## Why This Boundary Exists
Forking `nextcloud/server` would force aiNAS to own upstream patching and compatibility work too early. Pushing aiNAS logic into a traditional Nextcloud app would make the product harder to evolve outside the PHP monolith. The scaffold in this repository is designed to avoid both traps.
Forking `nextcloud/server` would force betternas to own upstream patching and compatibility work too early. Pushing betternas logic into a traditional Nextcloud app would make the product harder to evolve outside the PHP monolith. The scaffold in this repository is designed to avoid both traps.
## Responsibilities
@ -22,12 +22,12 @@ The shell app is responsible for:
- navigation entries
- branded entry pages inside Nextcloud
- admin-facing integration surfaces
- adapter calls into the aiNAS control plane
- adapter calls into the betternas control plane
The shell app is not responsible for:
- storage policy rules
- orchestration logic
- aiNAS-native RBAC decisions
- betternas-native RBAC decisions
- product workflows that may later be reused by desktop, iOS, or standalone web clients
### Control-plane service
@ -35,7 +35,7 @@ The shell app is not responsible for:
The control plane is responsible for:
- domain logic
- policy decisions
- internal APIs consumed by aiNAS surfaces
- internal APIs consumed by betternas surfaces
- Nextcloud integration adapters kept at the service boundary
### Shared contracts
@ -48,7 +48,7 @@ The local development stack uses Docker Compose so developers can bring up:
- Nextcloud
- PostgreSQL
- Redis
- the aiNAS control-plane service
- the betternas control-plane service
The Nextcloud shell app is mounted as a custom app and enabled through `./scripts/dev-up`.