beagle-turso 0.1.2-aarch64-linux → 0.1.3-aarch64-linux
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +24 -0
- data/lib/beagle/turso/version.rb +1 -1
- data/lib/beagle_turso/3.3/beagle_turso.so +0 -0
- data/lib/beagle_turso/3.4/beagle_turso.so +0 -0
- data/lib/beagle_turso/4.0/beagle_turso.so +0 -0
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 7c85e31d72fe11ab6eb70dc416b1fa4b3782e541955746f4290a7009c3443868
|
|
4
|
+
data.tar.gz: 199dd3f0118dcde3a7ca0455ef48e21aed47e1e207eb3821868b6be9a04f57a3
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: aa4f7a9c455413d71e5bd7ebd635314de450f3a5ae2a6c88b5fd7adcf3cb149a627337855a3b517589f99b9c8399acd3b5738b5f7191aa0c594168379a512500
|
|
7
|
+
data.tar.gz: 631490722ccb8880afe922e511153a693710f8fa6250e3ddf9e21f09c155e03db7b6551616742e7bda1e93b7db8482f1dc8aa3a0adba651898d7bb88bc71a9c0
|
data/README.md
CHANGED
|
@@ -79,6 +79,30 @@ called; `push` is not called automatically after every write. Until a
|
|
|
79
79
|
`push` succeeds, a write that's durable locally is not yet visible to other
|
|
80
80
|
replicas of the same remote database.
|
|
81
81
|
|
|
82
|
+
## Which Turso database?
|
|
83
|
+
|
|
84
|
+
Point a synced database at a Turso database **dedicated to this engine** —
|
|
85
|
+
ideally a fresh, empty one. On first open of an empty local replica,
|
|
86
|
+
`bootstrap_if_empty` pulls the remote down; against a fresh remote that's a
|
|
87
|
+
clean start, and the engine then manages its own state in that database (it
|
|
88
|
+
creates `turso_cdc`, `__turso_internal_*`, and `turso_sync_last_change_id`
|
|
89
|
+
tables and takes an **exclusive lock** on the local replica file — only one
|
|
90
|
+
OS process may hold a given replica open at a time).
|
|
91
|
+
|
|
92
|
+
Two things to avoid:
|
|
93
|
+
|
|
94
|
+
- **Don't co-host a synced database with the legacy libSQL/Hrana driver.**
|
|
95
|
+
This engine (Turso's newer Rust core) and the classic libSQL client have
|
|
96
|
+
different write/sync models; running both against the same remote database
|
|
97
|
+
at once risks corrupting its sync state. Give this engine its own database.
|
|
98
|
+
- **Migrating an existing, populated libSQL database into the synced engine
|
|
99
|
+
is not validated.** A fresh database is the supported, tested path. If you
|
|
100
|
+
must adopt existing data, treat it as unproven — test push/pull round-trips
|
|
101
|
+
before relying on it.
|
|
102
|
+
|
|
103
|
+
A single remote database, dedicated to this engine and written by one process
|
|
104
|
+
at a time, is the model it's built for.
|
|
105
|
+
|
|
82
106
|
## Credential safety
|
|
83
107
|
|
|
84
108
|
`auth_token` is never included in `inspect` output or in error messages —
|
data/lib/beagle/turso/version.rb
CHANGED
|
Binary file
|
|
Binary file
|
|
Binary file
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: beagle-turso
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.3
|
|
5
5
|
platform: aarch64-linux
|
|
6
6
|
authors:
|
|
7
7
|
- BeagleSoftwareUK
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2026-08-
|
|
11
|
+
date: 2026-08-09 00:00:00.000000000 Z
|
|
12
12
|
dependencies: []
|
|
13
13
|
description: |
|
|
14
14
|
A Ruby driver for Turso's database engine, backed by a native Rust
|