MMDVM Server Project for Multiple Servers in the Same Virtual Machine

Group Description

This group will be used to document our efforts to roll out 2 or more MMDVM to IPSC servers (AKA: Bridget) on the same VM.

Please provide your first name and call sign in your subscription/profile after your request to join has been made.  If you do not do this you will not be be joining our group.  Think of it as a simple test to follow instructions.

UPDATE: We have our first multiple instances running on a single VM with the great help by Dylan KI7SBI.  He has published his work on GitHub.  What we still lack is the install scripting and documentation that enables a 2 or 3 instance install using a newly spun-up VM (at Digital Ocean).  That is in the works and normal workloads and the holidays have slowed out effort to publish the script and documentation.  But it is coming...
It is not a general MMDVM support group but a specific effort for the common man to be able to roll out their own multiple servers on the same machine.  While we have a narrow focus, we will share the fruits of our efforts with other neophyte groups who wish to deploy their own MMDVM services for their members.  Or consider this an in-house effort to discuss how to and best approach to, this goal.

We are using the cool project that W0MJS, Cort has spearheaded and others have contributed to over the years.  See the overall project at:  Github and join their Forum if you are interested in their work.

We have wanted to be able to offer an easy method to stack up our MMDVM servers on the same VM so that multiple MMDVM devices could access different talkgroup decks to various c-Bridges (via IPSC).  Then to publish the method so that others (like us) who know little about Linux would be able to deploy these multiple servers.

As our busy Bridget here at PNW DMR is only using about 11% CPU on a minimal DO 1 core VM, we think we can stack up 4 or 5 more "Bridgets", so to speak on a single monthly service.  Memory use is the larger factor over that of CPU as our early 2 stack is using about 300 MB RAM

Likely others have done this already and it is not a big deal but the secret sauce hasn't trickled down to us yet.  While others have lent a hand in the past with Screen and one other method I don't recall now, we were stuck until Dylan came to our rescue with his Docker implementation.

If you would like to help, let us know.  If you request to join, please update your profile/bio if we don't already know you.  Here's how

Group Information

  • 38 Members
  • 28 Topics, Last Post:
  • Started on
  • Feed

Group Settings

  • This is a subgroup of DMR-Main.
  • All subscribers can post to the group.
  • Posts to this group do not require approval from the moderators.
  • Posts from new users require approval from the moderators.
  • Messages are set to reply to group.
  • Subscriptions to this group require approval from the moderators.
  • Archives are visible to anyone.
  • Wiki is visible to subscribers only.
  • Only moderators can create hashtags.
  • Members can edit their posts.


No integrations.

Top Hashtags [See All]

 or  Log In If You Are Already A Member

Message History

Group Email Addresses