How the NUC is set up
The hard drive should have Ubuntu 22.04 installed, along with ROS2 Humble, TAMProxy (a staff microcontroller library), and a git repository set up. The default user is named team-X (where X is your team number) with the password balsam (we encourage you to change this, but do not forget your password!!!). Your user has superuser permissions.
Your team should do most of your work in the ~/team-X folder, where there is a skeleton git repository already set up.
Inside your team's repository there should be a colcon_ws folder, which is an empty ROS2 workspace, should you opt to use ROS2.
PollMeMaybe
The majority of the time, your NUC will be mounted to your robot, powered by a DeWalt Battery, and connected to who knows which MIT WiFi routers around campus. As a result, one will need to find the NUC's IP address to SSH into the NUC and control it that way.
We recommend you use the MIT network and have one of your team mates login using their access key.
All the NUCs are preconfigured to report their current IP address to PollMeMaybe, a rudimentary webservice we built to solve this problem. Once your NUC comes online it will poll the site every minute so you can copy the IP and SSH in.
Pushing git commits from the NUC
The NUC has an SSH key that is configured as a deploy key with write access to your team's github repo. Basically this means you can push from the NUC without doing any funky authentication things (This is how the initial commits were pushed)