feat: Node Install, Start, Stop, Upgrade ENG-572

[HashMapsData2Value]

ℹ Overview

📝 Related Issues

✅ Acceptance:

• Pre-commit checks pass

[codecov]

Codecov Report

Attention: Patch coverage is 15.98891% with 909 lines in your changes missing coverage. Please review.

Project coverage is 56.06%. Comparing base (9dfe545) to head (694564c).
Report is 52 commits behind head on main.

Files with missing lines	Patch %	Lines
cmd/configure/configure.go	0.83%	238 Missing ⚠️
internal/algod/mac/mac.go	0.00%	228 Missing ⚠️
internal/algod/linux/linux.go	39.31%	87 Missing and 1 partial ⚠️
internal/algod/fallback/algod.go	0.00%	60 Missing ⚠️
internal/system/cmds.go	18.84%	55 Missing and 1 partial ⚠️
cmd/configure/utils.go	0.00%	53 Missing ⚠️
internal/algod/algod.go	30.55%	50 Missing ⚠️
internal/algod/utils/utils.go	0.00%	47 Missing ⚠️
cmd/node/debug.go	0.00%	23 Missing ⚠️
cmd/node/node.go	33.33%	12 Missing and 6 partials ⚠️
... and 6 more

Additional details and impacted files

@@             Coverage Diff             @@
##             main      #25       +/-   ##
===========================================
- Coverage   68.70%   56.06%   -12.65%     
===========================================
  Files          44       60       +16     
  Lines        3934     5012     +1078     
===========================================
+ Hits         2703     2810      +107     
- Misses       1078     2019      +941     
- Partials      153      183       +30     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[HashMapsData2Value]

I SSH:ed into an Ubuntu EC2 (exact AMI: ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-20241109) and ran these initial commands

sudo apt-get upgrade -y && sudo apt-get update -y
git clone https://github.com/algorandfoundation/hack-tui.git
sudo apt-get install golang-go -y
cd hack-tui
git checkout feat/algod-node-install
go build . && sudo ./algorun-tui node install
sleep 10
export TOKEN=$(cat /var/lib/algorand/algod.admin.token)
curl http://localhost:8080/v2/participation -H "X-Algo-API-Token: $TOKEN" | grep “null"
./algorun-tui -a http://localhost:8080 -t $TOKEN

When I later tried the node configure command, I got the following:

I assume that Ubuntu should be supported.

Btw, should we align the configuration command to be the same as how we handle sudo with the node commands?

[HashMapsData2Value]

Running the sudo ./algorun-tui configure service command on my Mac resulted in this output (regardless of whether the node was running or not). I'm not sure what the point is?

Perhaps we shouldn't release the configure command at all at this stage? Unless we can return it to how it was before, with the long set of prompts and the actual editing of the service files?

[HashMapsData2Value]

One more comment - I realize it might not be strictly within the confines of this PR, but I do think that if a user has used ./algorun-tui to do a node install, and given that the node debug command shows the location of the data directory, I do believe that the user should be able to do ./algorun-tui without any endpoint or token flag and have the command figure out on its own to grab the token and try the default http://localhost:8080 endpoint .

On the off-chance that there is a separate algod running on that endpoint the token will fail to authenticate and we will know what's wrong. If there's no algod at all then the tui can complain, or perhaps use some other mechanism to search through the user's ports and find the correct one.

From a UX perspective I think even for me (who contributed to this PR) it is cumbersome to have to type out ./algorun-tui -a http://localhost:8080 -t $TOKEN 😅

[PhearZero]

I assume that Ubuntu should be supported.

This is poor naming on the command, it is very limited in scope and relates to the next comment

Running the sudo ./algorun-tui configure service command on my Mac resulted in this output (regardless of whether the node was running or not). I'm not sure what the point is?

Perhaps we shouldn't release the configure command at all at this stage? Unless we can return it to how it was before, with the long set of prompts and the actual editing of the service files?

I'll try to think of a way to clean it up or name it appropriately. I want to provide an interface for writing the plist file for power users. I was using it heavily at first and decided to dogfood it with the installer.

I do believe that the user should be able to do ./algorun-tui without any endpoint

I have a pretty good idea on how to bring enough of the configuration command over without biting off too much.
Let's tackle this in the bootstrap process, we can tackle all the commands at once for a final polish 🎉