Go to file
fyears 8671ba4660 use loglevel everywhere 2022-01-05 00:23:49 +08:00
.github/workflows add env to build 2021-12-04 01:46:40 +08:00
assets/branding use loglevel everywhere 2022-01-05 00:23:49 +08:00
docs fix enc base64url doc test 2021-12-31 20:55:13 +08:00
src use loglevel everywhere 2022-01-05 00:23:49 +08:00
tests split settings and fix format 2021-12-31 23:46:52 +08:00
.editorconfig force editors 2021-10-23 15:48:42 +08:00
.gitattributes lfs track more imgs 2021-12-11 22:47:16 +08:00
.gitignore ignore more 2021-11-15 23:36:44 +08:00
.prettierignore avoid rewriting dist main.js 2021-10-24 20:40:30 +08:00
LICENSE add license 2021-10-21 09:53:20 +08:00
README.md statement that only support onedrive for personal currently 2022-01-03 20:35:19 +08:00
esbuild.config.mjs basically working onedrive 2021-12-29 00:35:46 +08:00
manifest.json 0.2.7 2022-01-03 01:04:45 +08:00
package.json use loglevel everywhere 2022-01-05 00:23:49 +08:00
styles.css basically working onedrive 2021-12-29 00:35:46 +08:00
tsconfig.json esbuild is way faster 2021-11-27 14:49:07 +08:00
versions.json 0.2.7 2022-01-03 01:04:45 +08:00
webpack.config.js basically working onedrive 2021-12-29 00:35:46 +08:00

README.md

Remotely Save

This is yet another unofficial sync plugin for Obsidian. If you like it or find it useful, please consider give it a star GitHub Repo stars on Github.

BuildCI

Latest release: 0.2.7) Old release: 0.2.6) Old release: 0.2.5)

Disclaimer

!!!Caution!!!

As of Jan 2022, the plugin is considered in BETA stage. DO NOT USE IT for any serious vaults. ALWAYS, ALWAYS, backup your vault before using this plugin.

Features

  • Supports:
    • Amazon S3 or S3-compatible
    • Dropbox
    • OneDrive for personal
    • Webdav
  • Obsidiain Mobile supported. Vaults can be synced across mobile and desktop devices with the cloud service as the "broker".
  • End-to-end encryption supported. Files would be encrypted using openssl format before being sent to the cloud if user specify a password.
  • Minimal Intrusive.
  • Fully open source under Apache-2.0 License.
  • Sync Algorithm open for discussion.

Limitations

  • Users have to trigger the sync manually. This design is intentional because the plugin is in beta, and it's better for users to be exactly aware of the running of this plugin.
  • "deletion" operation can only be triggered from local device. It's because of the "minimal intrusive design". May be changed in the future.
  • No Conflict resolution. No content-diff-and-patch algorithm. All files and folders are compared using their local and remote "last modified time" and those with later "last modified time" wins.
  • Cloud services cost you money. Always be aware of the costs and pricing.
  • All files or folder starting with . (dot) or _ (underscore) are treated as hidden files, and would NOT be synced. It's useful if you have some files just staying locally. But this strategy also means that themes / other plugins / settings of this plugin would neither be synced.

Questions, Suggestions, Or Bugs

You are greatly welcome to ask questions, post any suggestions, or report any bugs! The project is mainly maintained on GitHub:

Additionally, the plugin author may occasionally visit Obsidian official forum and official Discord server, and pay attention to this-plugin-related information there.

Download and Install

  • Option #1: You can search, download, and install the plugin in official "community plugin list".
  • Option #2: You can also use Obsidian42 - BRAT to install this plugin. Input fyears/remotely-save in the configuration of BRAT.
  • Option #3: GitHub release (latest by SemVer and asset including pre-releases) Manually download assets (main.js, manifest.json, styles.css) from the latest release.
  • Option #4: BuildCI Every artifacts are placed in the "Summary" under every successful builds. It's automatically generated by every commit, may break something.

Usage

S3

  • Prepare your S3 (-compatible) service information: endpoint, region, access key id, secret access key, bucket name. The bucket should be empty and solely for syncing a vault.
  • Configure (enable) CORS for requests from app://obsidian.md and capacitor://localhost and http://localhost. It's unfortunately required, because the plugin sends requests from a browser-like envirement. And those addresses are tested and found on desktop and ios and android.
  • Download and enable this plugin.
  • Enter your information to the settings of this plugin.
  • If you want to enable end-to-end encryption, also set a password in settings. If you do not specify a password, the files and folders are synced in plain, original content to the cloud.
  • Click the new "switch" icon on the ribbon (the left sidebar), every time you want to sync your vault between local and remote. (No "auto sync" yet.)
  • Be patient while syncing. Especially in the first-time sync.

Dropbox

  • This plugin's function for Dropbox is not as mature as functions for S3.
  • This plugin is NOT an official Dropbox product. The plugin just uses Dropbox's public API.
  • After the authorization, the plugin can read your name and email (which cannot be unselected on Dropbox api), and read and write files in your Dropbox's /Apps/remotely-save folder.
  • If you decide to authorize this plugin to connect to Dropbox, please go to plugin's settings, and choose Dropbox then follow the instructions.
  • Password-based end-to-end encryption is also supported. But please be aware that the vault name itself is not encrypted.

OneDrive for personal

  • This plugin's function for OneDrive is not as mature as functions for S3.
  • This plugin is NOT an official Microsoft / OneDrive product. The plugin just uses Microsoft's OneDrive's public API.
  • This plugin only works for "OneDrive for personal", and not works for "OneDrive for Business" (yet). See #11 to further details.
  • After the authorization, the plugin can read your name and email, and read and write files in your OneDrive's /Apps/remotely-save folder.
  • If you decide to authorize this plugin to connect to OneDrive, please go to plugin's settings, and choose OneDrive then follow the instructions.
  • Password-based end-to-end encryption is also supported. But please be aware that the vault name itself is not encrypted.

webdav

  • webdav support is considered experimental.
  • Currently only supports BASIC authorization method.
  • Currently webdav server has to be enabled CORS for requests from app://obsidian.md and capacitor://localhost and http://localhost, AND all webdav HTTP methods, AND all webdav headers. These are required, because Obsidian mobile works like a browser and mobile plugins are limited by CORS policies.
    • Popular software NextCloud, OwnCloud, rclone serve webdav do NOT enable CORS by default. If you are using any of them, you should evaluate the risk, and find a way to enable CORS, before using this plugin.
    • The plugin is tested successfully under python package wsgidav (version 4.0). See this issue for some details.
  • Your data would be synced to a ${vaultName} sub folder on your webdav server.
  • Password-based end-to-end encryption is also supported. But please be aware that the vault name itself is not encrypted.

Import And Export Not-Oauth2 Plugin Settings By QR Code

It's often verbose / inconvenient to input not-oauth2 credentials on mobile. (On different desktop computers, it's trivial to copy and paste data.json across different devices.)

So this plugin has a helper function to export those settings as a QR code, then you could use mobile device's camera to import the settings.

Attention:

  1. Oauth2 - related information is omitted. It means that Dropbox, OneDrive login credentials are NOT included in the QR Code.
  2. Please, NEVER share the QR Code to others. It's as equivalent to the login credentials.

Steps:

  1. Configure the plugin settings on one device, and make sure the sync functions work. (E.g, you could sync notes using S3 credentials.)
  2. Open plugin settings page. Then scroll down the page, until the section "Import and Export Settings". Click the button "Get QR Code". A new modal should show up and you should see a QR code.
  3. On a second device, make sure the vault name is the same as the first device's.
  4. On that second device, use its camera app, or any apps that support scanning QR codes, to scan the QR code from the first device. (On latest iOS, the system's built in camera app should work. On Android, at least one open source app Binary Eye is tested to be working.)
  5. A link / url / address should be identified in the scan-QR-code app, and you could follow the instruction in the app, and then you should be redirected to open the Obsidian app.
  6. And finally, there should be a new notice in the Obsidian app saying the settings are successfully imported. Otherwise please check the error message in the notice.