Connect

Local Connection

Unless you changed any settings, RioDB should be listening on HTTPS port 2333.
You can test it by opening https://localhost:2333/ on a browser, and see the following response:
{"status": 200, "message":"RioDB here. Tell me WHEN."}

On linux, you can try curl:

curl -k https://localhost:2333

All commands will be addressed to that same URL. The default ‘admin’ password is RioDB!
Statements are posted as text/plain payload, and must end with a semi-colon. For example, to run the command"system status;"

curl -k -u admin:RioDB! https://localhost:2333 -d 'system status;'

You can also use the REST client of your choice. But for convenience, if isolated in a closed network, you can use the RioDB console:

./riodb.sh console

or on windows:

riodb console

All examples in these documents assume all commands are being run in the console or in a Rest client, without the CURL stuff. But you can do anything with CURL.

Special thanks to northern-64bit !
…for creating the open-source console for RioDB. If your instance does not have network access or is unreachable from a REST client, you can use the console utility to run RioDB commands locally.
RioDB-Headless-Client

Remote Connection

Using a REST client like Bruno, Postman or Insomnia, you should be able to connect to the RioDB server using HTTPS on port 2333 (unless you changed it).

https://<riodb server>:2333

If you deployed RioDB on a cloud provider, ensure that the RioDB server, or subnet, has inbound rules allowing traffic from the system running the REST Client, such as your home or work IP Address.

If the RioDB server is strictly in a private subnet, then you may need to use the local connection method.

The default credentials are admin:RioDB! and we encourage you to change it as soon as possible.

From the REST client, you can send one or many commands to RioDB, but each command must end with a semicolon:

system status;