Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
ostool-server
ostool-server is the board management server for ostool.
It provides:
- board allocation and lease management
- remote serial terminal access
- TFTP session file handling
- a systemd-friendly deployment model on Linux
Install
Before installing ostool-server, make sure Node.js and pnpm are available in your environment.
The crate build process compiles the bundled web UI, so cargo install will fail if either tool is missing.
You can download and install Node.js from:
https://nodejs.org/en/download
After Node.js is installed, install pnpm with:
Install directly with curl
The install script can be executed directly from GitHub:
|
The script will:
- install
ostool-serverwithcargo install - install the binary to
/usr/local/bin/ostool-server - stop an existing
ostool-serversystemd service if present - recreate
/etc/ostool-server - install
/etc/systemd/system/ostool-server.service - start the service if you confirm it
If the script is executed remotely and the local ostool-server.service template is unavailable, it will automatically download the matching service template from:
https://raw.githubusercontent.com/drivercraft/ostool/main/ostool-server/scripts/ostool-server.service
Install from local source
If you already have the repository locally:
Upgrade
To upgrade an existing ostool-server installation while preserving the current config and data:
You can also run the upgrade script directly from GitHub:
|
To upgrade from a local checkout instead of crates.io:
Configuration
The default config path is:
/etc/ostool-server/config.toml
If the config file does not exist, ostool-server will create it automatically on first start and write the generated defaults back to disk.
The default listen address is:
0.0.0.0:2999
Useful Commands