So, just in case it helps someone I have a finalized list of my ufw commands for a server that is intended to be a web server that connects to a back end storage solution mounted with fuse, (the fuse implementation communicates to the storage service over http).
I fairly exhaustively went through the list of standard ports (not completely exhaustively just fairly... so I likely added more than are needed and probably missed a few).
I utilized /etc/server as well as the wikipedia list of ports and various other articles led me there...
Anyway here are the commands in order:
ufw default deny incoming
ufw default deny outgoing
ufw limit 22/tcp
ufw allow 9418/tcp
ufw limit <your custom SSH port here if not 22>/tcp
ufw allow 80
ufw allow 443
ufw allow out 80
ufw allow out 443
ufw allow out 53
ufw allow out 37
ufw allow out 101
ufw allow out 161
ufw allow out 135
ufw allow out 427
ufw allow out 43
ufw allow out 115
ufw allow out 525
ufw allow out 123
ufw allow out 873
ufw allow out 989
ufw allow out 990
ufw allow out 530
ufw allow out 546
ufw allow out 547
ufw allow out 593
In the way of a bit of explanation, Apache = port 80, Apache Secure = 443, (and had to put it in quotes for the command to go through).
Port 9418 is for git (though it can use various protocols), 530 & 546 are IPV6, 530 & 593 are both rpc related.
Also SSH doesn't go over UDP (thus the /tcp on the second command).
Again hope that helps someone.
The above previously did NOT fully allow apt-get to work (I thought it did but when I went to do apt-get update I was getting odd results were the progress seemed to get stuck).
Anyway I also failed to notice this line from the man page:
ufw supports both ingress and egress filtering and users may optionally
specify a direction of either in or out for either incoming or outgoing
traffic. If no direction is supplied, the rule applies to incoming
(emphasis added by me, cause, well it needs it).
Turns out, along with the DNS port (53) you have to have outgoing HTTP/HTTPS ports enabled in order to have apt-get function properly (makes sense... and wget will surely appreciate this too & any webservices, & probably many get repositories, etc...).