Thanks, I’d suggest updating the official ‘node install’ documents though. 
https://developer.algorand.org/docs/run-a-node/setup/install/ - even calls out betanet explicitly in its instructions at the end (implying it’s correct).
The link you provided even calls it out as the first thing in its ‘requirements’ but then provides different directions in the doc itself. I got things working with the -g flag
What’s the difference between devnet and betanet?
Perfect, thanks. As a new enthusiast/dev to Algorand, it would be helpful if there was a clear description/diagram of the various nets and how/when they’re used. It’s not clear to me what networks I want to have synced and when I might need to use them. testnet/mainnet is fairly clear (to me at least). betanet/devnet seems a little hand-wavy though and the discrepancies in the documentation (prob more complete lack of mention really) doesn’t help.
ie: If I go to developer.algorand.org and search for devnet (https://developer.algorand.org/search/?query=devnet&sort_by=relevancy&category=all-categories) - zero results are returned.
There is a brief allusion to it here - https://developer.algorand.org/docs/run-a-node/operations/switch_networks/ - but agreed, a table of networks and purposes would be helpful.
I personally recommend using the sandbox tool for most local purposes as it can be quickly caught up for most chains from the snapshots. (https://medium.com/algorand/introducing-sandbox-the-quick-way-to-get-started-on-algorand-8082c2d18854)
My company also offers a free to use Algod API if you need fully synced, archived, ledgers with indexing. (https://developer.purestake.io)