Skip to content

Latest commit

 

History

History
111 lines (85 loc) · 7.64 KB

README.md

File metadata and controls

111 lines (85 loc) · 7.64 KB
Raw

Joplin-Terminal-Data-API

A docker image to provide the Joplin's Data API externally, containing all features of Joplin Terminal as well as some optimization schemes suitable for headless use

Introduction: Joplin Terminal

The Joplin application offers an interactive application based on CLI, a command executor based on command-line arguments, and a Data API. The differences among these are as follows:

  • Interactive Application (by running joplin): Mimics the interface and user experience of Joplin Desktop on PC, suitable for direct use by users in environments without GUI.
  • Command-line arguments (by running joplin <command>): Provides a variety of commands that can execute some programmatic functionalities directly, not suitable for direct use by users, only suitable for operation by administrators. Can be run directly in the shell, or in the interactive application by omitting the prefix joplin and using the :<command> format instead.
  • Data API (by calling http://:41184): Offers RESTful CRUD services for several data entities such as notes, notebooks, tags, etc. Initially exclusive for data transfer with the Joplin Web Clipper plugin, but later found to also be suitable for the development of various peripheral software based on Joplin's data. Cannot modify Joplin configurations, not suitable for direct use by users.

Deployment

docker pull rickonono3/joplin-terminal-data-api:latest

There are only one port(for synchronizing to OneDrive maybe two), and a config file folder necessary you need to map:

Port/Volumn Necessary Description
9967 ✗ OneDrive OAuth Service
41184 ✗ Joplin Data API
41185 ✓ Joplin Data API (AutoToken)
/root/joplin ✓ The folder stored Joplin config file

Configuration

Mount a host folder to container's /root/joplin, and create a config file named joplin-config.json inside.

By executing command joplin help config in a container terminal，we can find all the configuration keys of Joplin. And，we can get an example of the config file:

{
  "dateFormat": "DD/MM/YYYY",
  "folders.sortOrder.field": "title",
  "layout.folderList.factor": 1,
  "layout.note.factor": 2,
  "layout.noteList.factor": 1,
  "locale": "en_GB",
  "net.proxyTimeout": 1,
  "notes.sortOrder.field": "user_updated_time",
  "notes.sortOrder.reverse": true,
  "revisionService.enabled": true,
  "revisionService.ttlDays": 90,
  "showCompletedTodos": true,
  "sync.8.url": "https://s3.amazonaws.com/",
  "sync.interval": 300,
  "sync.maxConcurrentConnections": 5,
  "sync.target": 5,
  "sync.wipeOutFailSafe": true,
  "timeFormat": "HH:mm",
  "trackLocation": true,
  "uncompletedTodosOnTop": true
}

Since the container re-imports the configuration with joplin config --import < /root/joplin/joplin-config.json every time it restarts, using the command joplin config <key> <value> in the container terminal will become ineffective upon the next restart. Write all configurations need to be persistently saved into joplin-config.json.

Data API

For API Request/Response formats, see Joplin Data API Document。

In the original Joplin setup, using the Data API first requires obtaining a Clipper Token with the confirmation by the user from Joplin client. Since it is not easy to be performed with Joplin CLI, especially in Docker containers, here we use a universal token instead. This token has already been automatically filled in every request to the Data API through the Nginx reverse proxy. Therefore, the port you use to call the Data API is not Joplin's original 41184 port, but Nginx's 41185. For requests sent to 41185, there is no need to manually provide a token (unlike the method described in Joplin documentations). Use it at your own risk.

If you really still want to understand in detail:

cat /root/.config/joplin/settings.json | grep 'token' | sed 's/^.*"\([^"]*\)".*$/\1/g'

# (Example) The printed universal API token which appended as query string by Nginx RevProxy:
# f724edfab395...

E2EE

The usage of command joplin e2ee is introduced by command joplin help e2ee:

e2ee <command> [path]

    Manages E2EE configuration. Commands are `enable`, `disable`, `decrypt`, `status`, 
    `decrypt-file`, and `target-status`.

    -p, --password <password>  Use this password as master password (For security reasons, it is not 
                               recommended to use this option).
    -v, --verbose              More verbose output for the `target-status` command
    -o, --output <directory>   Output directory
    --retry-failed-items       Applies to `decrypt` command - retries decrypting items that 
                               previously could not be decrypted.

Generally, using joplin e2ee enable -p <password> can complete the automatic encoding and decoding during synchronization.

Synchronization

For sync targets other than OneDrive, configure directly as follows:

  1. Configure the sync target in joplin-config.json according to the introduction in stdout of joplin help config
  2. Execute joplin sync inside the container, and follow the prompts (if exist) to complete the configuration.

Below, we mainly discuss the synchronization for OneDrive.

Since the OneDrive sync target requires login from Microsoft, and the Microsoft login is only available in a web GUI, Joplin uses a temporary external server for login authentication, which is on port 9967. However, using a GUI web browser in a CLI environment is too hard. After reading the Joplin target code, We offer the following solutions:

Solution 1: The host machine has a GUI, and the 9967 port can be mapped

  1. Map port 9967 to 9967 (it must be exactly 9967, and the port is only used once during the login to OneDrive. If you do not want to map to this port, please use Solution 2)
  2. Ensure that "sync.target" in the configuration file is 3, if not, configure it and restart the container
  3. Attach a new terminal into the container, execute joplin sync, it will show that you need to visit http://127.0.0.1:9967/auth, access it on the host machine, complete all steps to finish the synchronization configuration

Solution 2: The host machine does not have a GUI, or the 9967 port is not available

  1. Ensure that "sync.target" in the configuration file is 3, if not, configure it and restart the container
  2. Attach a terminal into the container, execute joplin sync, it will show that you need to visit http://127.0.0.1:9967/auth, do not follow it.
  3. On any safe computer with a GUI, access the following URL: https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=e09fc0de-c958-424f-83a2-e56a721d331b&scope=files.readwrite+offline_access+sites.readwrite.all&redirect_uri=http%3a%2f%2flocalhost%3a9967&response_type=code&prompt=login. This step is equivalent to a piece of Joplin source code
  4. After completing the last step in the browser, you will be redirected to http://localhost:9967/?code=<onedrive_auth_code>(^1). At this point, it will be 404 not found. Let's attach a new terminal in the container (now there are two terminals in the container, one is the newly added sh, the other is joplin sync waiting for OneDrive login), copy the whole address(^1) from the browser, use wget in the container to access it once.
  5. Check the terminal running joplin sync, it should show that login was successful