mirror of
https://github.com/vrtmrz/obsidian-livesync.git
synced 2025-12-22 22:21:29 +00:00
bump
This commit is contained in:
@@ -1,7 +1,7 @@
|
|||||||
{
|
{
|
||||||
"id": "obsidian-livesync",
|
"id": "obsidian-livesync",
|
||||||
"name": "Self-hosted LiveSync",
|
"name": "Self-hosted LiveSync",
|
||||||
"version": "0.24.26",
|
"version": "0.24.27",
|
||||||
"minAppVersion": "0.9.12",
|
"minAppVersion": "0.9.12",
|
||||||
"description": "Community implementation of self-hosted livesync. Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
|
"description": "Community implementation of self-hosted livesync. Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
|
||||||
"author": "vorotamoroz",
|
"author": "vorotamoroz",
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
{
|
{
|
||||||
"name": "obsidian-livesync",
|
"name": "obsidian-livesync",
|
||||||
"version": "0.24.26",
|
"version": "0.24.27",
|
||||||
"description": "Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
|
"description": "Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
|
||||||
"main": "main.js",
|
"main": "main.js",
|
||||||
"type": "module",
|
"type": "module",
|
||||||
|
|||||||
64
updates.md
64
updates.md
@@ -1,3 +1,19 @@
|
|||||||
|
## 0.24.27
|
||||||
|
|
||||||
|
### Improved
|
||||||
|
|
||||||
|
- We can use prefix for path for the Bucket synchronisation.
|
||||||
|
- For example, if you set the `vaultName/` as a prefix for the bucket in the root directory, all data will be transferred to the bucket under the `vaultName/` directory.
|
||||||
|
- The "Use Request API to avoid `inevitable` CORS problem" option is now promoted to the normal setting, not a niche patch.
|
||||||
|
|
||||||
|
### Fixed
|
||||||
|
|
||||||
|
- Now switching replicators applied immediately, without the need to restart Obsidian.
|
||||||
|
|
||||||
|
### Tidied up
|
||||||
|
|
||||||
|
- Some dependencies have been updated to the latest version.
|
||||||
|
|
||||||
## 0.24.26
|
## 0.24.26
|
||||||
|
|
||||||
This update introduces an option to circumvent Cross-Origin Resource Sharing
|
This update introduces an option to circumvent Cross-Origin Resource Sharing
|
||||||
@@ -30,18 +46,18 @@ However, just to whisper, this is tremendously fast.
|
|||||||
|
|
||||||
- Automatic display-language changing according to the Obsidian language
|
- Automatic display-language changing according to the Obsidian language
|
||||||
setting.
|
setting.
|
||||||
- We will be asked on the migration or first startup.
|
- We will be asked on the migration or first startup.
|
||||||
- **Note: Please revert to the default language if you report any issues.**
|
- **Note: Please revert to the default language if you report any issues.**
|
||||||
- Not all messages are translated yet. We welcome your contribution!
|
- Not all messages are translated yet. We welcome your contribution!
|
||||||
- Now we can limit files to be synchronised even in the hidden files.
|
- Now we can limit files to be synchronised even in the hidden files.
|
||||||
- "Use Request API to avoid `inevitable` CORS problem" has been implemented.
|
- "Use Request API to avoid `inevitable` CORS problem" has been implemented.
|
||||||
- Less secure, please use it only if you are sure that you are in the trusted
|
- Less secure, please use it only if you are sure that you are in the trusted
|
||||||
environment and be able to ignore the CORS. No `Web viewer` or similar tools
|
environment and be able to ignore the CORS. No `Web viewer` or similar tools
|
||||||
are recommended. (To avoid the origin forged attack). If you are able to
|
are recommended. (To avoid the origin forged attack). If you are able to
|
||||||
configure the server setting, always that is recommended.
|
configure the server setting, always that is recommended.
|
||||||
- `Show status icon instead of file warnings banner` has been implemented.
|
- `Show status icon instead of file warnings banner` has been implemented.
|
||||||
- If enabled, the ⛔ icon will be shown inside the status instead of the file
|
- If enabled, the ⛔ icon will be shown inside the status instead of the file
|
||||||
warnings banner. No details will be shown.
|
warnings banner. No details will be shown.
|
||||||
|
|
||||||
### Improved
|
### Improved
|
||||||
|
|
||||||
@@ -55,7 +71,7 @@ However, just to whisper, this is tremendously fast.
|
|||||||
- We can purge the remote bucket again if we using MinIO instead of AWS S3 or
|
- We can purge the remote bucket again if we using MinIO instead of AWS S3 or
|
||||||
Cloudflare R2.
|
Cloudflare R2.
|
||||||
- Purging the remote bucket is now more reliable.
|
- Purging the remote bucket is now more reliable.
|
||||||
- 100 files are purged at a time.
|
- 100 files are purged at a time.
|
||||||
- Some wrong messages have been fixed.
|
- Some wrong messages have been fixed.
|
||||||
|
|
||||||
### Behaviour changed
|
### Behaviour changed
|
||||||
@@ -63,8 +79,8 @@ However, just to whisper, this is tremendously fast.
|
|||||||
- Entering into the deeper directories to gather the hidden files is now limited
|
- Entering into the deeper directories to gather the hidden files is now limited
|
||||||
by `/` or `\/` prefixed ignore filters. (It means that directories are scanned
|
by `/` or `\/` prefixed ignore filters. (It means that directories are scanned
|
||||||
deeper than before).
|
deeper than before).
|
||||||
- However, inside the these directories, the files are still limited by the
|
- However, inside the these directories, the files are still limited by the
|
||||||
ignore filters.
|
ignore filters.
|
||||||
|
|
||||||
### Etcetera
|
### Etcetera
|
||||||
|
|
||||||
@@ -104,25 +120,25 @@ However, just to whisper, this is tremendously fast.
|
|||||||
|
|
||||||
- Bucket synchronisation has been enhanced for better performance and
|
- Bucket synchronisation has been enhanced for better performance and
|
||||||
reliability.
|
reliability.
|
||||||
- Now less duplicated chunks are sent to the server. Note: If you have
|
- Now less duplicated chunks are sent to the server. Note: If you have
|
||||||
encountered about too less chunks, please let me know. However, you can send
|
encountered about too less chunks, please let me know. However, you can send
|
||||||
it to the server by `Overwrite remote`.
|
it to the server by `Overwrite remote`.
|
||||||
- Fetching conflicted files from the server is now more reliable.
|
- Fetching conflicted files from the server is now more reliable.
|
||||||
- Dependent libraries have been updated to the latest version.
|
- Dependent libraries have been updated to the latest version.
|
||||||
- Also, let me know if you have encountered any issues with this update.
|
- Also, let me know if you have encountered any issues with this update.
|
||||||
Especially you are using a device that has been in use for a little
|
Especially you are using a device that has been in use for a little
|
||||||
longer.
|
longer.
|
||||||
|
|
||||||
## 0.24.23
|
## 0.24.23
|
||||||
|
|
||||||
### New Feature
|
### New Feature
|
||||||
|
|
||||||
- Now, we can send custom headers to the server.
|
- Now, we can send custom headers to the server.
|
||||||
- They can be sent to either CouchDB or Object Storage.
|
- They can be sent to either CouchDB or Object Storage.
|
||||||
- Authentication with JWT in CouchDB is now supported.
|
- Authentication with JWT in CouchDB is now supported.
|
||||||
- I will describe steps later, but please refer to the
|
- I will describe steps later, but please refer to the
|
||||||
[CouchDB document](https://docs.couchdb.org/en/stable/config/auth.html#authentication-configuration).
|
[CouchDB document](https://docs.couchdb.org/en/stable/config/auth.html#authentication-configuration).
|
||||||
- A JWT keypair for testing can be generated in the setting dialogue.
|
- A JWT keypair for testing can be generated in the setting dialogue.
|
||||||
|
|
||||||
### Improved
|
### Improved
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user