So it turns out that the documentation of getting remote access set up on the Raspberry Pi is really straightforward.
I’ve been using a combination of three articles, all through the same site. Then end result is that this is a ridiculously easy setup, and the only annoying part will be switching between mouse and keyboard.
The second is the more complicated setup, but still fairly easy. There’s little reason not to set up a graphical login for the Pi, unless you really like the idea of having only the command line and never even the option of using anything else.
I’m using wireless instead of ethernet, and I’ve unfortunately yet to see if that will give me any additional problems with the final step below.
All of this being said, the Raspberry Pi practically begs to be set up remotely, which is good, because setting it up physically with monitors, keyboard, internet, and mouse is kind of a pain in the neck.
One of the things I was worried about going into development on the Pi was that stuff like this would end up being a really annoying timesink that would get in the way of doing actual development. Thankfully that’s not the case.