Our core mission is driving the future of distributed cloud computing. The infrastructure of the internet is siloed and byzantine. We can do better.

GRAVITL

I'm sure eveyone could have a slightly different default set of expectations, however, it does seem good to have one or two "best-practice" deployment models.

Personally, I think simple is good, but the 'status quo" of a default installation has been changing rapidly, so it's a little confusing.

My personal thoughts:
1) by default, super simple, self-contained client-mode  as it is on 0.8.5 is probably best for most out-of-box testing... big caveat, should be called out that users can't SSH back to the netmaker host via the wireguard networks
2) next most simple situation, disable self-contained client-mode and install netclient natively on the host... as <@!232509546919100416> just mentioned there is the NODE_ID/MAC_ADDRESS issue... so maybe server uses NODE_ID  `netmaker-server` by default, and the `netclient` install could still use existing default NODE_ID    ... This could be documented for "if you desire SSH into netmaker host over wireguard network, and don't mind joining the netmaker host client to networks".
3) docker based server+client with host access is by far the messiest and most confusing... it could be documented for advanced use cases, but really, `netclient` solution sounds nicer to me