Skip to main content

DMRHub Notes

So after getting the installation done, and working out some of the kinks, here are some things to know about this:

  1. The server utilizes a third party ham DMR radio ID registration service for it's repeater and user authentication. Currently, server admins cannot add a repeater to the server without it being registered there. Same goes for users. Those wishing to register on the server must have valid ID/Callsign from that provider first.
    1. The work around to this is to build the binary from source and replace the DB with a compressed json file, which an example is provided
    2. The server automatically updates it's information from that third party at midnight, daily
    3. This is an exercise for another day, and as such, the current installation is default as fuck - with the third party registration  requirements
  2. My installation instructions were written as I went along, and as I encountered problems, I updated my instructions with my fixes, such as updating commands to work with my ish on my hardware. As such, it may be a departure from the official deployment guide, which I linked to, so use your research skills to un-ass anything you run into, based on your own implementation
  3. The server is sitting idle, unused and will remain as such until such a time I can build my own binary (time constraints at this point). As a result, it does not have a public URL to access the dashboard and is only reached via my LAN
  4. As far as updating this when a new release hits, I have no clue how that works, but I suspect it should be as simple as replacing the DMRHub executable in the appropriate directory, as all the other things required, like PSQL, Redis, and the env file have already been implemented, so we shall see what that looks like - I am interested to see how much of the to-do list the developer gets done between now and the next release. Depending on that, I may or may not update (with the default binary he builds), and if there is enough cause, I may build my own binary with the update then
  5. As always, this is a continuous project, and any updates will be reflected on this site. Until then, stay frosty
Back to top