Difference between revisions of "Murmur"

From Alpine Linux
Jump to: navigation, search
m (Installation)
m (Tried running the original command and received an error. Looked up the error and it seems the command has changed.)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[https://wiki.mumble.info/wiki/Running_Murmur Murmur] (also called Mumble-Server) is the server component for [https://wiki.alpinelinux.org/wiki/Mumble Mumble]. Murmur allows you to run your own private or public voice chat server for the Mumble client.
+
[https://wiki.mumble.info/wiki/Running_Murmur Murmur] (also called Mumble-Server) is the server component for [https://wiki.alpinelinux.org/wiki/Mumble Mumble]. Mumble is an open source, cross platform, low-latency, high quality voice over IP (VoIP) client. Mumble uses a client/server architecture and is primarily used by gamers, but can be used for any VoIP purpose.
  
 
== Installation ==
 
== Installation ==
 
First of all we need Murmur in our server.
 
First of all we need Murmur in our server.
 
{{Cmd|apk add murmur}}
 
{{Cmd|apk add murmur}}
Open the murmur.ini configuration file and edit it so murmur can be run by the 'murmur' user created by the package.
+
 
{{Cmd|vim /var/lib/murmur/murmur.sqlite}}
+
=== Setting up SSL certificates ===
{{Cat|/var/lib/murmur/murmur.sqlite|<nowiki>
+
If you already have used Certbot to set up certificates in your web server, then you can easily make a new certificate for a subdomain 'mumble' and add the cert paths to the mumble.ini configuration file. You can use vim and edit the file manually.
uname=murmur
+
{{Cmd|vim /etc/murmur.ini}}
 +
It should look something like this.
 +
{{Cat|/etc/murmur.ini|<nowiki>
 +
sslCert=/etc/letsencrypt/live/your_domain.com/fullchain.pem
 +
sslKey=/etc/letsencrypt/live/your_domain.com/privkey.pem
 
</nowiki>
 
</nowiki>
 
}}
 
}}
Now give permissions to the murmur database, so the user 'murmur' can read it.
 
{{Cmd|chown murmur /var/lib/murmur/murmur.sqlite}}
 
  
 
=== Starting up the service ===
 
=== Starting up the service ===
Start the murmur service.
+
Start the Murmur service.
 
{{Cmd|rc-service murmur start}}
 
{{Cmd|rc-service murmur start}}
{{Note|Optional steps}}
+
You can add the Murmur service to the default runlevel.
You can add the murmur service to the default runlevel.
+
{{Cmd|rc-update add murmur default}}
{{Cmd|rc-service add murmur default}}
+
In case you don't want Murmur to be default on runlevel, rollback with this command
In case you don't want murmur to be default on runlevel, rollback with this command
+
{{Cmd|rc-update delete murmur default}}
{{Cmd|rc-service delete murmur default}}
+
 
 +
 
 +
[[category: telephony]]

Latest revision as of 08:30, 17 June 2020

Murmur (also called Mumble-Server) is the server component for Mumble. Mumble is an open source, cross platform, low-latency, high quality voice over IP (VoIP) client. Mumble uses a client/server architecture and is primarily used by gamers, but can be used for any VoIP purpose.

Installation

First of all we need Murmur in our server.

apk add murmur

Setting up SSL certificates

If you already have used Certbot to set up certificates in your web server, then you can easily make a new certificate for a subdomain 'mumble' and add the cert paths to the mumble.ini configuration file. You can use vim and edit the file manually.

vim /etc/murmur.ini

It should look something like this.

Contents of /etc/murmur.ini

sslCert=/etc/letsencrypt/live/your_domain.com/fullchain.pem sslKey=/etc/letsencrypt/live/your_domain.com/privkey.pem

Starting up the service

Start the Murmur service.

rc-service murmur start

You can add the Murmur service to the default runlevel.

rc-update add murmur default

In case you don't want Murmur to be default on runlevel, rollback with this command

rc-update delete murmur default