Murmur - Revision history

John3-16: Moved contents to new "Mumble" page, further to the preferred main program name (Mumble) upstream, including recent renaming of the murmur server to mumble-server See Talk:Mumble. Added redirect. Also: 1. "Mumble" wiki page had been referred to in the Beginning paragraph, but the page did not exist; 2. [https://wiki.mumble.info/wiki/Running_Murmur Murmur] was a broken link, but is now updated in the Mumble page; 3. mention of mumble.ini also needed updating, now named murmur.ini.

2026-02-01T04:50:00Z

Moved contents to new "Mumble" page, further to the preferred main program name (Mumble) upstream, including recent renaming of the murmur server to mumble-server See Talk:Mumble. Added redirect. Also: 1. "Mumble" wiki page had been referred to in the Beginning paragraph, but the page did not exist; 2. [https://wiki.mumble.info/wiki/Running_Murmur Murmur] was a broken link, but is now updated in the Mumble page; 3. mention of mumble.ini also needed updating, now named murmur.ini.

← Older revision		Revision as of 04:50, 1 February 2026
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]. 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.~~		#REDIRECT [[Mumble]]

	~~== Installation ==~~
	~~First of all we need Murmur in our server.~~
	~~{{Cmd\|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.
	~~{{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>~~
	}}

	~~== Running as a service ==~~

	~~=== Configuration ===~~
	~~Make sure this line is present in your murmur.ini:~~
	~~{{Cat\|/etc/murmur.ini\|<nowiki>~~
	~~pidfile=/var/run/murmur/murmur.pid~~
	~~</nowiki>~~
	}}
	~~This will allow OpenRC to track the status of the process.~~

	~~=== Starting up the service ===~~
	~~Start the Murmur service.~~
	~~{{Cmd\|rc-service murmur start}}~~
	~~You can add the Murmur service to the default runlevel.~~
	~~{{Cmd\|rc-update add murmur default}}~~
	~~In case you don't want Murmur to be default on runlevel, rollback with this command~~
	~~{{Cmd\|rc-update delete murmur default}}~~


	~~[[category: telephony~~]]

Floak: Document necessary pidfile step for openrc

2025-03-13T16:46:46Z

Document necessary pidfile step for openrc

@@ Line 14: / Line 14: @@
 </nowiki>
 }}
 === Starting up the service ===

Sunnythaper: Tried running the original command and received an error. Looked up the error and it seems the command has changed.

2020-06-17T08:30:29Z

Tried running the original command and received an error. Looked up the error and it seems the command has changed.

← Older revision		Revision as of 08:30, 17 June 2020
Line 19:		Line 19:
	{{Cmd\|rc-service murmur start}}		{{Cmd\|rc-service murmur start}}
	You can add the Murmur service to the default runlevel.		You can add the Murmur service to the default runlevel.
	{{Cmd\|rc-~~service~~ add murmur default}}		{{Cmd\|rc-update 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-~~service~~ delete murmur default}}		{{Cmd\|rc-update delete murmur default}}


	[[category: telephony]]		[[category: telephony]]

Nicolaus: /* Installation */

2019-10-13T21:58:52Z

Installation

← Older revision		Revision as of 21:58, 13 October 2019
Line 4:		Line 4:
	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}}~~
	~~{{Cat\|/var/lib/murmur/murmur.sqlite\|<nowiki>~~
	~~uname=murmur~~
	~~</nowiki>~~
	}}
	~~Now give permissions to the murmur database, so the user 'murmur' can read it.~~
	~~{{Cmd\|chown murmur /var/lib/murmur/murmur.sqlite}}~~

	=== Setting up SSL certificates ===		=== Setting up SSL certificates ===

Innsill: + category: telephony

2019-10-09T07:37:12Z

+ category: telephony

← Older revision		Revision as of 07:37, 9 October 2019
Line 30:		Line 30:
	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-service delete murmur default}}		{{Cmd\|rc-service delete murmur default}}


			[[category: telephony]]

Nicolaus at 06:33, 9 October 2019

2019-10-09T06:33:05Z

← Older revision		Revision as of 06:33, 9 October 2019
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 ==
Line 24:		Line 24:

	=== 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}}
	You can add the ~~murmur~~ service to the default runlevel.		You can add the Murmur service to the default runlevel.
	{{Cmd\|rc-service 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-service delete murmur default}}		{{Cmd\|rc-service delete murmur default}}

Nicolaus: /* Starting up the service */

2019-10-09T06:07:17Z

Starting up the service

← Older revision		Revision as of 06:07, 9 October 2019
Line 26:		Line 26:
	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-service 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-service delete murmur default}}		{{Cmd\|rc-service delete murmur default}}

Nicolaus: /* Setting up SSL certificates */

2019-10-09T06:07:09Z

Setting up SSL certificates

← Older revision		Revision as of 06:07, 9 October 2019
Line 14:		Line 14:

	=== Setting up SSL certificates ===		=== Setting up SSL certificates ===
	~~{{Note\|Optional steps.}}~~		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.
	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 ~~do it simple and slick with a single sed command. Or you can also~~ use vim and ~~do it~~ manually.		{{Cmd\|vim /etc/murmur.ini}}
	{{Cmd\|~~sed -i -e 's/;sslCert=/sslCert=\/etc\/letsencrypt\/live\/your_domain.com\/fullchain.pem/ ; s/;sslKey=/sslKey=\/etc\/letsencrypt\/live\/your_domain.com\/privkey.pem/'~~ /etc/murmur.ini}}
	It should look something like this.		It should look something like this.
	{{Cat\|/etc/murmur.ini\|<nowiki>		{{Cat\|/etc/murmur.ini\|<nowiki>

Nicolaus: Added simple SSL guide for Murmur

2019-10-09T06:05:13Z

Added simple SSL guide for Murmur

← Older revision		Revision as of 06:05, 9 October 2019
Line 12:		Line 12:
	Now give permissions to the murmur database, so the user 'murmur' can read it.		Now give permissions to the murmur database, so the user 'murmur' can read it.
	{{Cmd\|chown murmur /var/lib/murmur/murmur.sqlite}}		{{Cmd\|chown murmur /var/lib/murmur/murmur.sqlite}}

			=== Setting up SSL certificates ===
			{{Note\|Optional steps.}}
			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 do it simple and slick with a single sed command. Or you can also use vim and do it manually.
			{{Cmd\|sed -i -e 's/;sslCert=/sslCert=\/etc\/letsencrypt\/live\/your_domain.com\/fullchain.pem/ ; s/;sslKey=/sslKey=\/etc\/letsencrypt\/live\/your_domain.com\/privkey.pem/' /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>
			}}

	=== 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}}		{{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-service 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-service delete murmur default}}		{{Cmd\|rc-service delete murmur default}}

Nicolaus: /* Installation */

2019-10-09T04:58:16Z

Installation

← Older revision		Revision as of 04:58, 9 October 2019
Line 4:		Line 4:
	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.		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}}		{{Cmd\|vim /var/lib/murmur/murmur.sqlite}}
	{{Cat\|/var/lib/murmur/murmur.sqlite\|<nowiki>		{{Cat\|/var/lib/murmur/murmur.sqlite\|<nowiki>