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
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Visit the [Documentation](https://uos.github.io/minot) to find out more.
11
11
12
12
## Quick Install
13
13
14
-
For most users, the easiest way to install Minot is using the installation script with a single command. This will install the `minot`binary and `minot-coord` with sensible defaults for getting started.
14
+
For most users, the easiest way to install Minot is using the installation script with a single command. This will install the `minot`binaries and libraries into your user directory.
15
15
16
16
~~~bash
17
17
curl -sSLf https://install.steado.tech/minot | sh
@@ -21,10 +21,13 @@ For ROS support, make sure to have your ROS environment sourced before running t
21
21
22
22
After your first steps with Minot, you may want to use its more advanced features. Check the detailed [install page](https://uos.github.io/minot/installation.html) for that.
23
23
24
-
## VSCode Extension
24
+
## VS Code Extension
25
25
26
26
Search for "Minot" in your editor an install the package. Running it will require a Minot binary in your `$PATH`. The extension will add syntax highlighting for `.mt` files and automatically activates as soon as you open a Minot file. You will see some buttons in the editor footer. Select some lines and run them with `Run Selection`. Hover over the buttons to see their keybindings.
27
27
28
+
### Tree-sitter Support
29
+
30
+
Minot comes with support for Tree-sitter syntax highlighting outside of VS Code. See [this repository](https://github.com/stelzo/tree-sitter-minot) for instructions on how to add Minot support to the Helix editor or use the repository for other editors that support Tree-sitter grammars.
Copy file name to clipboardExpand all lines: docs/docs/installation.md
+17-15Lines changed: 17 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,22 @@
1
1
## Install Script (Recommended)
2
2
3
-
For most users, the easiest way to install Minot is using the installation script with a single command. This will install the `minot`binary and `minot-coord` with sensible defaults for getting started.
3
+
For most users, the easiest way to install Minot is using the installation script with a single command. This will install the `minot`binaries and libraries into your user directory.
4
4
5
5
~~~bash
6
6
curl -sSLf https://install.steado.tech/minot | sh
7
7
~~~
8
8
9
9
For ROS support, make sure to have your ROS environment sourced before running the script.
10
10
11
-
### VSCode Extension
11
+
### VS Code Extension
12
12
13
13
Search for "Minot" in your editor an install the package. Running it will require a Minot binary in your `$PATH`. The extension will add syntax highlighting for `.mt` files and automatically activates as soon as you open a Minot file. You will see some buttons in the editor footer. Select some lines and run them with `Run Selection`. Hover over the buttons to see their keybindings.
14
14
15
-
### Detailed Installation
15
+
### Tree-sitter Support
16
+
17
+
Minot comes with support for Tree-sitter syntax highlighting outside of VS Code. See [this repository](https://github.com/stelzo/tree-sitter-minot) for instructions on how to add Minot support to the Helix editor or use the repository for other editors that support Tree-sitter grammars.
18
+
19
+
### Advanced Installation
16
20
17
21
You can also download and run the install script manually for more control.
18
22
Use `--help` to see all available configurations of Minot.
@@ -28,9 +32,9 @@ The installation script will:
28
32
- Automatically detect your operating system and architecture
29
33
- Resolve to the newest compatible and stable version
30
34
- Download prebuilt binaries from GitHub releases if available
31
-
- Fall back to building from source with `cargo install` if needed
32
-
-Install binaries to `~/.local/bin` (customizable with `--dir`)
33
-
-Offer to install Rust automatically if needed for building from source
35
+
- Fall back to building from source using Rust if needed
36
+
-Copy binaries and libraries into your local user directory (customizable with `--dir`)
37
+
-Add the uninstall script (`minot-uninstall`) to the same directory for easy removal later
34
38
35
39
**Embedded Components:**
36
40
@@ -79,9 +83,9 @@ Archives not specific to a ROS distribution contain builds that can be used inde
79
83
80
84
While the prebuilt binaries cover many common use cases, you may need to build Minot from source to tailor it to your specific needs. Building from source requires the [Rust toolchain](https://www.rust-lang.org/tools/install) to be installed on your system.
81
85
82
-
## Minot TUI
86
+
## Minot bundled binary
83
87
84
-
To build the Minot TUI, there are some feature flags for embedding common network participants for convenience. A detailed list of supported flags can be found in the [Minot features definition](https://github.com/uos/minot/blob/main/minot/Cargo.toml#L45).
88
+
To build the Minot bundled binary, there are some feature flags for embedding common network participants for convenience. A detailed list of supported flags can be found in the [Minot features definition](https://github.com/uos/minot/blob/main/minot/Cargo.toml#L45).
85
89
86
90
With default settings, Minot builds with an integrated coordinator. When running the following command with no changes, you will get a `minot` binary with integrated Coordinator and a `minot-coord` binary, that is *just* a Coordinator. The standalone Coordinator is enough for sharing variables [with the rat library](./varshare.md#library).
87
91
@@ -102,7 +106,7 @@ cargo install \
102
106
103
107
---
104
108
105
-
The next version does not need any ROS1 or ROS2 installation to compile but it expects to find a node in the network if you try to query a Bagfile:
109
+
This next version does not need any ROS1 or ROS2 installation to compile but it expects to find a node in the network if you try to query a Bagfile:
106
110
107
111
~~~bash title="Minimal with embedded Coordinator"
108
112
cargo install \
@@ -121,7 +125,7 @@ cargo install \
121
125
122
126
## Standalone Coordinator
123
127
124
-
Installing Minot TUI as shown above will also build a standalone variant of the Coordinator. It is called `minot-coord` in your path.
128
+
Running `cargo install` as shown above will also build a standalone variant of the Coordinator. It is called `minot-coord` in your path.
125
129
126
130
## Standalone Wind Turbines (Bagfile Publishers)
127
131
@@ -186,7 +190,7 @@ And link with `-lrat`.
186
190
For using the Rust library, just add this to your dependencies in `Cargo.toml`.
187
191
188
192
~~~toml title="Cargo.toml"
189
-
rat = { version = "0.1.0-rc.6", git = "https://github.com/uos/minot" }
193
+
rat = { version = "0.1.0", git = "https://github.com/uos/minot" }
190
194
~~~
191
195
192
196
## Ratpub (Native Publish/Subscribe)
@@ -195,7 +199,7 @@ Ratpub is only available for Rust. It uses Tokio for async I/O.
195
199
For using the library in your project, add these lines to your dependencies in `Cargo.toml`.
196
200
197
201
~~~toml title="Cargo.toml"
198
-
ratpub = { version = "0.1.0-rc.6", git = "https://github.com/uos/minot" }
202
+
ratpub = { version = "0.1.0", git = "https://github.com/uos/minot" }
199
203
tokio = { version = "1", features = ["full"] }
200
204
~~~
201
205
@@ -212,6 +216,4 @@ Learn more on how to use it in your Code by visiting the [feature page](./pubsub
212
216
213
217
## Uninstall
214
218
215
-
With modern software the word *"installing"* is overloaded. Cargo just compiles the code and moves the finished binaries to a directory in your path. There are no other side effects or files from Minot.
216
-
217
-
If you want to remove them, you can `minot uninstall` to uninstall minot or minot-coord. Or `cargo uninstall wind` for the manual installed binaries.
219
+
If you want to remove every file installed from the install script, you can run `minot-uninstall`. This executes a generated shell script that saved all added files and now removes them (including itself). You can also run `minot uninstall` to uninstall minot and minot-coord. Or `cargo uninstall wind` if you installed binaries with cargo.
0 commit comments