docs: add Journal definition and refine Object Storage setup guidance

Add an entry for Journal / Journal Sync to the project glossary under user-facing terms.

Update README.md table typography for WebRTC Peer-to-Peer.

In docs/setup_object_storage.md, add early navigation to manual setup, document CORS bypass via 'Use internal API', and align troubleshooting steps.
This commit is contained in:
vorotamoroz committed 2026-11-06 02:33:00 +00:00
1 parent 0942d461cf
commit a1e2120a8b
3 files changed
+13 -3

No files matched your search

+6 -2
View File
@@ -14,7 +14,7 @@ Prepare the following:
- an access key and secret key with access to the selected bucket;
- a bucket name and region;
- a unique bucket prefix when the bucket is shared or reserved for this Vault;
- CORS configuration permitting Obsidian's web origins (`app://obsidian.md`, `capacitor://localhost`, `http://localhost`) with `ETag` exposed; and
- CORS configuration permitting Obsidian's web origins (`app://obsidian.md`, `capacitor://localhost`, `http://localhost`) with `ETag` exposed (or enable `Use internal API` during setup to bypass CORS restrictions); and
- separate passphrases for Vault encryption and Setup URI encryption.
Back up every Vault involved, and do not use Obsidian Sync, iCloud synchronisation, or another synchronisation service on the same Vault.
@@ -32,9 +32,13 @@ Match your storage service credentials to the plug-in setup fields:
| Region specified by the provider (e.g., `auto` for R2) | `Region` | `region` |
| Folder prefix reserved for this Vault, such as `my-vault/` | `Folder Prefix` | `bucket_prefix` |
| Path-style addressing (required by some servers like MinIO) | `Use Path-Style Access` | `force_path_style` |
| Bypass CORS via Obsidian's native request API | `Use internal API` | `use_custom_request_handler` |
## Generate the initial Setup URI
> [!TIP]
> If you prefer to configure settings directly in Obsidian rather than using the command-line Setup URI generator, see [Configure the first device manually](#configure-the-first-device-manually).
The public generator applies the Object Storage preset and records the connection as the selected remote profile. Run it from a trusted terminal:
```sh
@@ -131,7 +135,7 @@ If you prefer to configure settings directly in Obsidian rather than using the D
3. Configure `End-to-End Encryption` and enter a strong Vault encryption passphrase. Save this passphrase securely.
4. Select the S3-compatible Object Storage option and proceed to `S3/MinIO/R2 Configuration`.
5. Enter your bucket settings using the [Setting fields reference](#setting-fields-reference) table above.
6. Select `Test Settings and Continue`. If the connection test fails, verify the API endpoint, credentials, bucket permissions, region, and CORS configuration.
6. Select `Test Settings and Continue`. If the connection test fails, verify the API endpoint, credentials, bucket permissions, and region. If CORS blocks the request or cannot be configured on your bucket, enable `Use internal API` to route requests through Obsidian's native HTTP handler.
7. Proceed to `Restart and Initialise Server`, then complete the confirmation steps as described in [Set up the first device](#set-up-the-first-device).
8. Once your test note synchronises, follow [Generate the second-device Setup URI](#generate-the-second-device-setup-uri) to connect subsequent devices easily.