-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rosbridge documentation should migrate to ros.org #28
Comments
+1 |
+1 On Mar 13, 2013, at 5:53 AM, Brandon Alexander notifications@github.com wrote:
|
The status quo will have to remain until a capable and trustworthy maintainer can be found to put a sustainable solution in place. |
Howdy, I left this as a ticket at kforge (http://kforge.ros.org/rosbridge/trac/ticket/14943), and thought I should add it here too since I'm not sure where rosbridge lives at the moment. I think the following should be added to the readme / wiki: I got the rosbridge server running on Ubuntu 12.10 with ros groovy using the following commands: # Go to catkin workspace
cd ~/catkin_ws
# Prepare catkin environment
source devel/setup.bash
# Get current rosbridge suite
cd src
git clone https://github.com/RobotWebTools/rosbridge_suite.git
# Also get rosauth, a dependency for rosbridge_server
git clone https://github.com/WPI-RAIL/rosauth.git
# Build and install new packages
cd ..
catkin_make
catkin_make install
# Start the rosbridge web server!
rosrun rosbridge_server rosbridge_websocket |
Thanks @uozuAho for the input! This repository (https://github.com/RobotWebTools/rosbridge_suite) is the correct location for Rosbridge 2.0. I'm actually working on overhauling the rosbridge documentation on ros.org this weekend. I'll be sure to add your instructions as well. |
The debian package for Thanks for the feedback @uozuAho ! |
Whoops, I responded too quickly. The preferable way to install is |
Thanks for the quick responses guys. Looking forward to the new documentation! |
The rosbridge documentation has been updated at http://ros.org/wiki/rosbridge_suite, including information for each individual package and tutorials on getting started. The original kForge repository has been removed to avoid future confusion and the Rosbridge 2.0 Protocol Specification document has been converted to Markdown and placed in the GitHub repo. @uozuAho - your instructions were added to the Developing Rosbridge tutorial. |
I tried to install rosbridge suite like @baalexander commented but it was not successful. This is what I get |
Based on your GitHub post, it looks like you are using Ubuntu 12.10. ROS Electric is not known to work on anything past Ubuntu 11.10. Furthermore, if you take a look at the command you are using, you are attempting to install a ROS Groovy package which will not work with an Electric installation. rosbridge_suite is written for ROS Fuerte and ROS Groovy. Based on the output of your command, it looks like you do not have the ROS sources setup on your Ubuntu installation. Check out http://www.ros.org/wiki/groovy/Installation/Ubuntu to see how to set this up on Ubuntu 12.10. If you have do this already, be sure and try sudo apt-get update to refresh your sources list. If all else fails, you can install rosbridge from source using the comments posted in #28 (comment). |
Most rosbridge users will be using the documentation on ros.org. Currently, if you search around for rosbridge on the site, you find one of two things: the old rosbridge with a depreciation notice that can be easily overlooked (someone even released it into groovy...?) or the new rosbridge with a completely blank page.
At the very least, install and run commands should be put up. I also feel the protocol itself should be clearly displayed on the WIKI in HTML. Currently the protocol is hidden on a page within a PDF. Since rosbridge should really be thought of as a protocol, it is important to have this information clearly available. Furthermore, since rosbridge is still "young", it will make it easier to suggest and collaborate on protocol enhancements.
The text was updated successfully, but these errors were encountered: