Conference Computer Configuration

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.

1. docker & docker compose setup on Ubuntu 22.04 LTS
2. visudo and add my non-privilidged account
3. Since the creation script drops my SSH key into root, as root, cp .ssh/authorized_keys ~mpayne/.ssh/ and set the permissions right
4. as unprivilidged account:
   1. curl -s "https://get.sdkman.io" | bash to install sdkman.io
   2. curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash to install nvm
   3. Add myself to the docker group, install mosh, & jq

  sudo usermod -aG docker ${USER}
  sudo apt-get install mosh tmux jq git

1. Setup the tmux status bar to something not default. e.g.

➜ cat ~/.tmux.conf 
set -g status-bg blue

1. Thanks to Dave B for suggesting that I add the command number to the prompt: export PS1="\! ${PS1}" at the bottom of .bashrc
2. Add set number to .vimrc

Docker Compose and localhost

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.

---

Tags: configurations, conferences, mosh

← Back home