Skip to content

Releases: n0012/neogdsync

1.1.0 — auto sync

Choose a tag to compare

@n0012 n0012 released this 05 Sep 19:58

Auto sync on a timer (Settings → Sync), default off, minimum 1 minute. Quiet by design: a notice only when files actually moved or a run failed; a ⏱ in the status bar shows it is armed. An idle run is a single Drive API call, so a 1-minute interval is affordable at any vault size.

Settings are also reorganised into Step 1 (OAuth client) → Step 2 (refresh token) → Step 3 (vault root folder), with a banner naming whatever is still missing.

1.0.14 — documented own-client setup + token script

Choose a tag to compare

@n0012 n0012 released this 05 Sep 19:55

No behaviour change to sync. Adds scripts/get-refresh-token.mjs for minting a refresh token against your own OAuth client, a full setup guide, and settings copy that says where the token comes from and how to regenerate it.

1.0.13 — own OAuth client, no hosted sign-in

Choose a tag to compare

@n0012 n0012 released this 05 Sep 19:45

Client ID / Client secret now appear above the refresh token, and the "Connect Google Drive" button is hidden once direct mode is on — that button consents to the proxy's OAuth client, so its token could never be redeemed against your own.

Fill in this order: Client ID → Client secret → Vault root folder ID → Refresh token.

1.0.12 — optional own OAuth client

Choose a tag to compare

@n0012 n0012 released this 05 Sep 19:38

Fork of martinlegend/neogdsync v1.0.11 with one addition: Client ID and Client secret settings. When both are set, token refresh goes straight to oauth2.googleapis.com and the auth proxy is bypassed, so a Drive-scoped refresh token never leaves the device. Blank = upstream behaviour.

Install with BRAT: n0012/neogdsync.