As RobotWebTools/rosbridge_suite#157 has been merged.

tornado is now in rosbridge_tools.

Usage

https://github.com/RobotWebTools/rosbridge_suite/blob/develop/rosbridge_server/scripts/rosbridge_websocket.py#L42-L46

The current implementation forces to use www as a package web root. If we utilise package export, each package can have different web page root. It would give users freedom to choose web root directory.

For example, roswww uses www directory as a web page root whereas my_webapp_package uses apps directory as a page root.

# package.xml in roswww
<export>
  <roswww_root>www</roswww_root>
</export>

# package.xml in my_webapp_package
<export>
  <roswww_root>apps</roswww_root>
</export>

Other usecases(rocon_app) reference,

• package export tag crawler
• where package export tag crawler is called
• example package.xml in rocon_apps package

I don't know where the community for this package lives, so I am asking here even though this is not an issue. I am looking to host a simple web server on my Ros robot. Basically responding to HTTP GETs returning status html pages, or to HTTP POSTs to tell the robot to do something. This will allow me to create a non-ROS client on a mobile or just a web browser.

• I am not clear whether this library only serves up static html pages or can respond with custom code to any http request, executing ROS code as a result.

• Can you point me to a sample where this package is used so I can see how to do various things?

They both contain tornado and it is installed by both. Just install the two packages to reproduce.

Is a version for ROS noetic planned? I created a pull request with the necessary changes for compatibility with python3 #49

I think I was expecting with #32 on http://docs.ros.org/jade/api/roswww/html/index.html that API page is auto-generated, in addition to the rosdoc-generated rst page we currently see. After #32 merged in I still don't see it.

Is there any plan to release a melodic version?

Continued from #13 (comment)
Confirmed with de2d9e0 on Indigo, Trusty

Error description updated:

$ rosrun roswww webserver.py then accessing http://localhost:8000 doesn't return (web browser keeps trying on and on). When I kill webserver.py's process, browser immediately shows "server not found", so I assume the browser is able to connect to the webserver (webserver log file might help here..).

I regret this proposal wasn't that right for the following reasons:

• Another package in this repository (roswww_pack) doesn't seem to be used, at least within roswww so that roswww can be released by itself.
• Single package can be released w/o metapkg.

Actually I've already modified the repository name to roswww.

Since roswww is now merged into rwt_ros (see tork-a/rwt_ros#2 (comment)), keeping a separate repository might be just confusing. roswww used to be released into ROS Groovy too, but it was withdrawn.

Just curios. If not how about renaming branch as something general? like develop in rosbridge_suite?

Single page applications do client side routing, but the application only have a singe page doing all the work. I'm proposing to add a flag to make this possible by serving the default page index.html for all 404 Not Found requests. Flag: --single-page-app (debatable)

I would also propose another option to only serve the content from a single package at the root of this server. This is useful for serving control interface applications for a specific system. Flag: --single-pkg=mypackage (debatable)

My use case is that I have a single page application that I am using as the control interface for my robot application that I would like to bundle and serve with the rest of my control software. I do not need to serve files from more than this single package.

I'm opening this issue to discuss if these are wanted functionality and if so, the API. I'm willing to submit a PR if you are interested.

Based on the decision here. This should fix issue #1

roswww should depend on rosbridge_tools rather than rosbridge_server.

tornado is soon to be in rosbridge_tools package. #146 #147 #149

@k-okada is there any plan to release 0.1.12 in kinetic ?

I was looking into roswww implementation to utilise as webserver which does not bring any ros_comm related dependencies.

The following was requiring ros dependency in roswww

• Logger(rospy.loginfo,logwarn...)
• rosparam for port parameterization
• rospack shell command
• tornado

I would like to propose changes to keep ROS dependency minimal in roswww

• Logger - It would not necessary to ros logger since it is webserver. Rather to use stdio or python logger
• rosparam - replaceable with command line argument.
• rospack shell command - It is necessary. rospack dependency should not be a problem. It is pure C++ module which does not bring ros_comm
• tornado - I have proposed to separated out tornado from rosbridge_server. RobotWebTools/rosbridge_suite#147

Then roswww package will only depend on

• rosbridge_tools : for tornado
• rospack : for package crawl script

Continued from a discussion.

For those who are interested in making this happen, please voice up here.

(As one of the maintainers, personally I'm not planning to spend any of my time on this in the forseeable future.)

So that you can't either import nor execute.
In version 0.1.2.

https://github.com/tork-a/roswww/blob/develop/package.xml