Having a linux computer in the cloud to avoid downloading a lot over the conference wifi.
Using mosh means the terminal connection doesn't go away from home to hotel hotspot:
mosh --port 1025 hostname tmux -a
Here's a list of setups I like. Having a long running server is not good because servers should not be pets.
visudo
and add my non-privilidged accountcp .ssh/authorized_keys ~mpayne/.ssh/
and set the permissions rightcurl -s "https://get.sdkman.io" | bash
to install sdkman.iocurl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash
to install nvm sudo usermod -aG docker ${USER}
sudo apt-get install mosh tmux jq git
➜ cat ~/.tmux.conf
set -g status-bg blue
export PS1="\! ${PS1}"
at the bottom of .bashrc
set number
to .vimrc
During Nebraska Code, I learned that just doing a docker compose up -d
will expose ports to the whole Internet. Yikes! I had a redis server open to the whole Internet for a while during a Wednesday workshop. After a bunch of googling and talking to folks I found a stackoverflow that led to this commit (reference & notes are in the commit).
After this is setup, use SSH tunnels to access things running on the server as if they were running on localhost.