|
| 1 | +--- |
| 2 | +title: "Launching RapidRecast" |
| 3 | +description: "How you can launch RapidRecast and the options available." |
| 4 | +summary: "" |
| 5 | +date: 2023-09-07T16:04:48+02:00 |
| 6 | +lastmod: 2023-09-07T16:04:48+02:00 |
| 7 | +draft: false |
| 8 | +weight: 810 |
| 9 | +toc: true |
| 10 | +seo: |
| 11 | + title: "" # custom title (optional) |
| 12 | + description: "" # custom description (recommended) |
| 13 | + canonical: "" # custom canonical URL (optional) |
| 14 | + noindex: false # false (default) or true |
| 15 | +--- |
| 16 | + |
| 17 | +# Downloading RapidRecast |
| 18 | + |
| 19 | +Pick up the latest release from the [Releases Page](http://localhost:1313/releases/). |
| 20 | + |
| 21 | +Download for the appropriate platform from the table at the bottom of the release page. |
| 22 | + |
| 23 | +Unpack wherever is convenient for you, for example `~/local/bin`. |
| 24 | + |
| 25 | +# Starting RapidRecast |
| 26 | + |
| 27 | +Once you have downloaded and unpacked RapidRecast, you should be able to run it immediately with this command. |
| 28 | + |
| 29 | +```bash |
| 30 | +# (Optional) configure logging |
| 31 | +export RUST_LOG=rapidrecast=trace,info |
| 32 | +# Start RapidRecast |
| 33 | +rapidrecast -p 0.0.0.0:0 -a 127.0.0.1:0 |
| 34 | +``` |
| 35 | + |
| 36 | +The above command creates an HTTP protocol and an Admin API on any available port. |
| 37 | +The `0.0.0.0` binding means that it is accessible on any network interface (such as the internet, if the firewall allows it). |
| 38 | +We do not want the Admin API accessible from anyone outside our computer though - so we have set the bind to be `127.0.0.1`. |
| 39 | +Only you can access it from your computer that way. |
| 40 | + |
| 41 | +Exposing the Admin API to the internet is considered safe, assuming the login credentials are secure. |
| 42 | + |
| 43 | +# Protocols available |
| 44 | + |
| 45 | +RapidRecast exposes protocols on CLI provided ports. |
| 46 | + |
| 47 | +## Admin Protocol |
| 48 | + |
| 49 | +RapidRecast provides a way to remotely configure its behaviour and state. |
| 50 | + |
| 51 | +To make the Admin Protocol available, you provide the CLI with the `-a` or `--admin-bind` parameter. |
| 52 | + |
| 53 | +For example `rapidrecast -a 127.0.0.1:8080` will make the admin protocol available on port 8080 on your computer only, but not to outside networks. |
| 54 | + |
| 55 | +## Service Protocols |
| 56 | + |
| 57 | +**Service Protocols** are the protocols that users of the service interact with. |
| 58 | +They are entirely programmable from the admin API and console. |
| 59 | + |
| 60 | +In the current latest release the available protocols are: |
| 61 | + |
| 62 | +| Protocol | CLI args | Example | |
| 63 | +|----------|--------------------------------------|------------------| |
| 64 | +| HTTP 1.1 | `-p <bind>` and `--http-bind <bind>` | `-p 127.0.0.1:0` | |
| 65 | + |
| 66 | + |
| 67 | +# Admin credentials |
| 68 | + |
| 69 | +To access the admin API, you need to use admin credentials. |
| 70 | + |
| 71 | +In the early days of RapidRecast, the admin credentials are hardcoded to `admin` and `admin-password`. |
| 72 | + |
| 73 | +Once logged in as an admin, you can create users and roles fitting the permissions you would like to use. |
| 74 | + |
| 75 | +To read more about Policies and Roles, see the [RBAC Guide]({{< ref "/docs/guides/rbac.md" >}}). |
0 commit comments