You are here

Service Naming Convention

5 posts / 0 new
Last post
VE7KOD
Service Naming Convention

I searched high and low so I apologize if this has been discussed...

Is there a set (ideal) naming convention for services as their is for node names? 

nc8q
nc8q's picture
Service naming logic ~= node naming logic
<discussion>
Same logic.
All service names (host names) should/must be unique.
Beginning a service name with your callsign is a good and safe practice.
</discussion>
;-)
Would you like to see some examples?

73, Chuck

 
VE7KOD
Thank you Chuck
Thank you Chuck

I only noticed last night when I installed both the iperfspeed and MeshChat ipk. 
iperfspeed is easy enough to change but the meshchat uses the service name as the zone so there are multiple on our mesh with that zone name. 

73
Jesse
nc8q
nc8q's picture
Node name, Host name, Service name
Node name, Host name, Service name are 3 separate lists.
The Node name and the Host name must be unique.
The 'Advertised services' name can be common, but if it is a link
it can only 'point to' a DHCP Address Reservation on the (LAN) Host name
on the same device.
Notice that every MeshChat 'Service Name' link 'points to' a different MeshChat server.
I hope this helps, Chuck

 
VE7KOD
Thank you very much.. Exactly
Thank you very much.. Exactly what I was after.

Jesse

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer