Open-RMF Web is a collection of packages that provide a web-based interface for users to visualize and control all aspects of Open-RMF deployments. Quick start with docker; Getting started from source; API server; API client; RMF Dashboard Framework; Configuration; Contribution guide; Roadmap

Collection of messages which bridges the C++ components of RMF to the web interface

Full web application of Open-RMF: rmf-web. Start the backend API server via docker with host network access, using the default configuration. The API server will be accessible at localhost:8000 by default.

Root repository for the RMF software. Contribute to open-rmf/rmf development by creating an account on GitHub.

I have a project with a microservices architecture and RMF is one of the microservices involved. Instead of using the RMF Dashboard, I have my own frontend and server that I would like to use to communicate to RMF using the rmf API server and client.

Nov 19, 2024 · This thread is aimed at learning how to properly set up RMF Dashboard and API Server with a local keycloak authentication provider such that: User would see the Login Screen upon running RMF Web 0.2.0. User enters their given RMF Dashboard username and password to …

Full web application of Open-RMF: rmf-web. Start the backend API server via docker with host network access, using the default configuration. The API server will be accessible at localhost:8000 by default.

Hi, I wanted to try out the RMF Web UI with the RMF Demos before trying to use it with my own simulation world. I checked the RMF Web Github page, and it says that the Quick docker is enough to launch the RMF Web and to use it. For context, I am currently using ROS2 Humble on Ubuntu version 22.04.5.

Dec 9, 2024 · The quick-start contains pre-built rmf-web images to use with your rmf installation, no additional rmf-web installation steps are needed. It would be helpful if you can list the steps you have tried.

Edit: Just to make it clear, this set of instructions builds rmf and rmf-web in a "standard" docker container, which means it is highly likely that the issue is some misconfiguration on your machine. I'll check around and see what could be the cause, based on your logs and output.