You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+23-2Lines changed: 23 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,9 +39,30 @@ With its advanced real‑time update capabilities, DynaRust pushes live changes
39
39
***Use Case Example:** Imagine a web UI needing push notifications. Store device IDs as keys in a `devices` table. Use a separate `status` key in the same table. The frontend listens to `devices/subscribe/status`. The backend iterates through device keys, performs actions, and updates the `status` key, instantly notifying all listening frontends. Simple and blazing fast! ⚡️
40
40
41
41
***🔒 Security:**
42
-
Each record needs a Authorization header for PUT, DELETE operations, each record has an owner field. Metodology is: anyone can read, only the owner can write or delete
43
-
Each node requires a "secret" token (set by the `CLUSTER_SECRET` environment variable) to join a cluster.
42
+
Certainly! Here’s a more polished and highlighted version of the **Security** section, emphasizing clarity and best practices:
44
43
44
+
---
45
+
46
+
### 🔒 **Security**
47
+
48
+
- **Access Control:**
49
+
- **Read:** Anyone can read records.
50
+
- **Write/Delete:** Only the record’s owner (as specified in the `owner` field) can modify or delete it.
51
+
- **Enforcement:** All `PUT` and `DELETE` operations require an `Authorization` header. The server verifies that the requester matches the record’s owner.
52
+
53
+
- **Cluster Security:**
54
+
- Each node must present a **secret token** (set via the `CLUSTER_SECRET` environment variable) to join the cluster, ensuring only trusted nodes participate.
55
+
56
+
- **Transport Security (HTTPS):**
57
+
- All communication is secured with HTTPS by default.
58
+
- **Easy Certificate Generation:**
59
+
- Run `bash cert.sh`, provide a password, and a `.p12` certificate will be generated under the `cert/` directory.
60
+
- **Testing Mode:**
61
+
- Set `DYNA_MODE=http` to disable HTTPS (for testing only;**not recommended for production**).
62
+
63
+
---
64
+
65
+
**_Security is enforced at every layer: from user access to node-to-node communication, ensuring your data remains private and protected._**
45
66
***🌐 Distributed Storage:**
46
67
Data is automatically partitioned and spread across all nodes in the cluster.
0 commit comments