There are lots of args in standalone.launch and concert_client.launch to utilise rapp manager. Here is a proposal to create configurable env-hooks. These are the list of configurations which I frequently customise to use in waiterbot and turtlebot.

Proposed envs

ROBOT_NAME
ROBOT_DESCRIPTION
ROBOT_TYPE
RAPP_PACKAGE_WHITELIST
RAPP_PACKAGE_BLACKLIST
ROBOT_UNIQUE_NAME
CONCERT_WHITELIST
CAPABILITIES
CAPABILITIES_PARAMETERS
CAPABILITIES_PACKAGE_WHITELIST
CAPABILITIES_BLACKLIST
INTERACTIONS
INTERACTIONS_LIST
INTERACTION_ROSBRIDGE_ADDRESS
INTERACTION_ROSBRIDGE_PORT

Available args in rapp manager

Capabilities

capabilities
capabilities_parameters
capabilities_blacklist
capabilities_nodelet_manager_name
capabilities_package_whitelist
capabilities_server_name
Rapp manager
auto_rapp_installation
auto_start_rapp
rapp_package_whitelist
rapp_package_blacklist
robot_name
robot_type
robot_icon
screen
simulation
robot_descrtiption
Interactions
interactions
interactions_list
rosbridge_address
rosbridge_port
Concert Client.launch
concert_whitelist
robot_unique_name
local_machine_only
concert_whatch_period
firewall

robotics-in-concert / rocon_app_platform

Env-hook based configuration #266

Capabilities

Rapp manager

Interactions

Concert Client.launch