self-hosted/joplin
1
0
Fork 0
mirror of https://github.com/laurent22/joplin.git synced 2024-12-24 10:27:10 +02:00
Code Issues Releases Activity

Update architecture.md

Browse Source
This commit is contained in:
Laurent Cozic 2023-04-29 14:39:15 +01:00 committed by GitHub
parent 77789c0b17
commit c08f7de6bb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
readme/spec/architecture.md
View File

@ -2,9 +2,9 @@
Joplin as a project is organised around three main components: Joplin as a project is organised around three main components:
- The user applications (desktop, mobile and CLI) - The user applications: For [desktop](https://github.com/laurent22/joplin/blob/dev/readme/desktop.md), [mobile](https://github.com/laurent22/joplin/blob/dev/readme/mobile.md) and [CLI](https://github.com/laurent22/joplin/blob/dev/readme/terminal.md))
- Joplin Server - [Joplin Server](https://github.com/laurent22/joplin/blob/dev/packages/server/README.md)
- Web Clipper - [Web Clipper](https://github.com/laurent22/joplin/blob/dev/readme/clipper.md)
## User applications ## User applications
@ -16,7 +16,7 @@ The overall architecture for each application is as such:
- Back end: This is shared by all applications. It is made of: - Back end: This is shared by all applications. It is made of:
- Services: Provide high-level functionalities, such as the search engine, plugin system or database driver. - Services: Provide high-level functionalities, such as the [search engine](https://github.com/laurent22/joplin/tree/dev/packages/lib/services/searchengine), [plugin system](https://github.com/laurent22/joplin/tree/dev/packages/lib/services/plugins) or [synchroniser](https://github.com/laurent22/joplin/blob/dev/packages/lib/Synchronizer.ts).
- Models: The model layer sits between the services and database. They provide a higher level abstraction than SQL and utility functions to easily save data, such as notes, notebooks, etc. - Models: The model layer sits between the services and database. They provide a higher level abstraction than SQL and utility functions to easily save data, such as notes, notebooks, etc.