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: docs/2.installation.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ However, we strongly recommend **not** using it outside testing environments.
20
20
21
21
To use native binaries you need to download a bundle which is simply a ZIP file with all the necessary binaries that you'll ever need to develop on and deploy Skytable.
22
22
23
-
1.**First download the latest bundle** for your platform. You can find [download links on the releases page](https://github.com/skytable/skytable/releases/v0.8.2).
23
+
1.**First download the latest bundle** for your platform. You can find [download links on the releases page](https://github.com/skytable/skytable/releases/v0.8.3).
24
24
2.**Unzip the ZIP file**. You'll find the following binaries in the extracted archive:
25
25
-`skyd`: This is the database server binary which when started runs as a daemon, serving requests
26
26
-`skysh`: This is the Skytable shell and it provides a very helpful interactive REPL database client
@@ -72,7 +72,7 @@ The package will:
72
72
2. **Start the container**:
73
73
74
74
```shell
75
-
docker run -d --name skydb -p 2003:2003 skytable/skytable:v0.8.2
75
+
docker run -d --name skydb -p 2003:2003 skytable/skytable:v0.8.3
76
76
```
77
77
78
78
:::tip
@@ -85,14 +85,14 @@ message with the generated password.
85
85
1. **Download the bundle**: To be able to run queries you need to download the bundle as described above
86
86
2. **Create the data directory**: To ensure that our database is persistent and all our data doesn't vanish as soon as the container is terminated, we'll map the data directory to an actual directory on our local system.
87
87
>**Note:** Create a folder called `skytable`in a convenient location. We recommend having a directory in`$HOME/docker-containers` where you can store the Skytable container's data and any other containers that you might use. It's a great way to keep things organized.
88
-
3. **Create your configuration**: [Download this template file](https://raw.githubusercontent.com/skytable/skytable/next/examples/config-files/template.yaml) and place it into the directory you created. Update the password with your `root` password of choice.
88
+
3. **Create your configuration**: [Download this template file](https://raw.githubusercontent.com/skytable/skytable/v0.8.3/examples/config-files/template.yaml) and place it into the directory you created. Update the password with your `root` password of choice.
Copy file name to clipboardExpand all lines: docs/protocol/index.md
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,7 @@ We keep adding more and more data types with every release. So, if you're workin
17
17
:::
18
18
19
19
Here are some good to know things, before a deep dive into the various pieces of the protocol:
20
+
20
21
- The protocol is based on top of TCP, so if your programming language standard library has a TCP client (as most of them do) you can build a client
21
22
- You might find the [official implementation of the Rust client](https://github.com/skytable/client-rust) to be a good reference
22
23
- If you need help, ask! (on Discord, ping us on Twitter, just reach out!)
@@ -25,8 +26,8 @@ Here are some good to know things, before a deep dive into the various pieces of
25
26
## Protocol revisions and compatibility
26
27
27
28
-**What constitutes an incompatible protocol version?** A protocol version is considered incompatible if and only if:
28
-
- the queries sent by an older client can't be processed by the server or
29
-
- the **same** responses sent by *the server in question* can't be decoded by the older client
29
+
- the queries sent by an older client can't be processed by the server or
30
+
- the **same** responses sent by *the server in question* can't be decoded by the older client
30
31
- If newer protocol versions introduce newer data types that is *not* considered an incompatible version since as long as the encoding for the types introduced in the earlier protocol(s) remains unchanged
31
32
- Hence, the compatibility code for a protocol only changes when it is considered incompatible
32
33
@@ -39,3 +40,4 @@ Please note this list is only maintained post 0.8.0.
0 commit comments