Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Accepted Answer
I created a new droplet and replayed all of your commands without any errors to make sure you can create directories as normal user do this command
sudo chown -R tom:tom $HOME
To make sure tom is the owner of your home directory and all of its sub directories
Hope this helps
THAT DID IT!!! Thank you, @Mohsen47! Obviously the problem line was where I gave root, which I didn’t really understand was a user and not a privilege level, permissions–not tom.
What a huge relief!
Wait, but now I have another question. What is the difference between these two commands? Is that giving the user tom sudo privileges has NOTHING to do with the $HOME directory? I would assume that sudo privileges would just naturally be granted to that directory, but I’m beginning to suspect that’s nothing close to the truth.
# Give tom sudo privileges...
$ usermod -aG sudo tom
# ...but tom still can't even write to his
# own directory without this. WTF?
$ sudo chown -R tom:tom $HOME