BigBlueButton/bigbluebutton-Github
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
688aceb672
bigbluebutton-Github/bigbluebutton-client/resources/config.xml.template

73 lines
2.2 KiB
Plaintext
Raw Normal View History

- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
<?xml version="1.0" ?>
<config>
- move up one folder as it is common for dev and prod
2010-07-04 23:35:35 +08:00
<localeversion>0.7</localeversion>
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
<version>VERSION</version>
<help url="http://HOST/help.html"/>
<porttest host="HOST" application="video"/>
<modules>
- change how we put version in the SWF filename - make not executable
2010-07-04 22:54:35 +08:00
<module name="ChatModule" url="ChatModule.swf?v=VERSION"
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
uri="rtmp://HOST/bigbluebutton"
loadNextModule="ListenersModule"
onUserJoinedEvent="START"
onUserLogoutEvent="STOP"
/>
- change how we put version in the SWF filename - make not executable
2010-07-04 22:54:35 +08:00
<module name="ViewersModule" url="ViewersModule.swf?v=VERSION"
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
uri="rtmp://HOST/bigbluebutton"
- fix xml format
2010-06-11 02:54:47 +08:00
host="http://HOST/bigbluebutton/conference-session/enter"
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
onAppInitEvent="LOAD" loadNextModule="ChatModule"
onAppStartEvent="START"
onUserLogoutEvent="STOP"
/>
- change how we put version in the SWF filename - make not executable
2010-07-04 22:54:35 +08:00
<module name="ListenersModule" url="ListenersModule.swf?v=VERSION"
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
uri="rtmp://HOST/bigbluebutton"
recordingHost="http://HOST"
loadNextModule="DeskShareModule"
onUserJoinedEvent="START"
onUserLogoutEvent="STOP"
/>
- change how we put version in the SWF filename - make not executable
2010-07-04 22:54:35 +08:00
<module name="DeskShareModule" url="DeskShareModule.swf?v=VERSION" uri="rtmp://HOST/deskShare" onUserJoinedEvent="START" onUserLogoutEvent="STOP" loadNextModule="PhoneModule" />
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
- change how we put version in the SWF filename - make not executable
2010-07-04 22:54:35 +08:00
<module name="PhoneModule" url="PhoneModule.swf?v=VERSION"
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
uri="rtmp://HOST/sip"
onUserJoinedEvent="START"
onUserLogoutEvent="STOP"
loadNextModule="VideoconfModule"
/>
- change how we put version in the SWF filename - make not executable
2010-07-04 22:54:35 +08:00
<module name="VideoconfModule" url="VideoconfModule.swf?v=VERSION"
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
uri="rtmp://HOST/video"
onUserJoinedEvent="START"
onUserLogoutEvent="STOP"
Updated config.xml in bigbluebutton-client
2010-06-10 23:11:57 +08:00
loadNextModule="HighlighterModule"
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
/>
- change how we put version in the SWF filename - make not executable
2010-07-04 22:54:35 +08:00
<module name="HighlighterModule" url="HighlighterModule.swf?v=VERSION"
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
uri="rtmp://HOST/bigbluebutton"
onUserJoinedEvent="START"
onUserLogoutEvent="STOP"
Updated config.xml in bigbluebutton-client
2010-06-10 23:11:57 +08:00
loadNextModule="PresentModule"
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
/>
- change how we put version in the SWF filename - make not executable
2010-07-04 22:54:35 +08:00
<module name="PresentModule" url="PresentModule.swf?v=VERSION"
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
uri="rtmp://HOST/bigbluebutton"
host="http://HOST"
onUserJoinedEvent="START"
onUserLogoutEvent="STOP"
/>
<!-- new module in development:
- change how we put version in the SWF filename - make not executable
2010-07-04 22:54:35 +08:00
<module name="DynamicInfoModule" url="DynamicInfoModule.swf?v=VERSION"
- create a config.xml template so we can substitute build numbers to create config.xml. This way, we get around the caching problem of modules when we have new releases.
2010-06-09 05:33:16 +08:00
uri="rtmp://HOST/bigbluebutton"
host="http://HOST"
infoURL="http://HOST/client/conf/example-info-data.xml?user={userID}&role={role}&meetingID={meetingID}"
onUserJoinedEvent="START"
onUserLogoutEvent="STOP"
/>
-->
</modules>
</config>
Reference in New Issue Copy Permalink