Remove the signaling URI settings

it now can be determined automatically
master
Daniel Berteaud 10 years ago
parent d7bcb03061
commit d38be16526
  1. 4
      conf/settings.ini.dist
  2. 13
      templates/default/documentation.html.ep
  3. 2
      vroom.pl

@ -4,10 +4,6 @@
;user = 'vroom'
;password = 'password'
[signaling]
; URI sent to clients where they can find the signaling server
;uri = 'https://vroom.exmple.com'
[turn]
; The stun server sent to client. You can set it to your own stun server. Takes a comma separated list of full
; stun uri as defined by rfc7064

@ -280,19 +280,6 @@ cp /opt/vroom/conf/settings.ini.dist /opt/vroom/conf/settings.ini</pre>
</ul>
</p>
<h3 id="settings_signaling">
signaling
</h3>
<p>
This section is where you define your signaling server settings.
This is because VROOM was using a modified <a href="https://github.com/andyet/signalmaster">SignalMaster</a>
as signaling server, which could run on a separate server. Now, the signaling server is directly included in VROOM daemon
so this section might be removed in the future
<ul>
<li><strong>uri</strong>: The uri to reach VROOM (/socket.io will be added to reach the SocketIO server)</li>
</ul>
</p>
<h3 id="settings_turn">
turn
</h3>

@ -1743,7 +1743,7 @@ any '/api' => sub {
# Return configuration for SimpleWebRTC
elsif ($req->{action} eq 'get_rtc_conf'){
my $resp = {
url => $config->{'signaling.uri'},
url => Mojo::URL->new($self->url_for('/')->to_abs)->scheme('https'),
peerConnectionConfig => {
iceServers => []
},

Loading…
Cancel
Save