sysadmin - lesser daemon

09

Apr

Provisioning a Red Hat VirtualBox VM With Vagrant

In what I hope will be the last entry in the "Brent learns the basics of VM provisioning" series, I finally moved to using Hashicorp's Vagrant yesterday. I'm glad I took the time to mess around in VirtualBox itself first - I always like understanding what I'm working with before I move to abstractions - but Vagrant makes it significantly easier. Vagrant sets up SSH in your VM by default, which is a nice time-saver, and generally makes the process of automating VM setup quick and easy. Behold:

1) Install Vagrant & VirtualBox.

2) In your project folder, add the

Setting Up Port Forwarding on a VirtualBox RedHat VM With A NAT Network Adapter

OK, quickly discovered that I was less brilliant than I thought yesterday. It appears that for the functionality I wanted (both the ability to SSH into the VM and to port forward from my local machine to an application running on the VM) I need to use a NAT and not a bridge network.

I spent a while struggling with this and discovered that to assign your VM to the standard 10.0.2.* range and successfully connect to the internet, a NAT drive should be your first network adapter. I'd initially had a bridge network as Adapter 1 and

Setting Up TiddlyWiki on a Remote Server with Systemd & Nginx

TiddlyWiki is a cool tool, but if you, like me, are ~~insane~~ interested in getting it set up on the cloud, it can be a bit of a hassle. Here's a quick set of instructions to get it to run automatically as a service on a Linux server - I used a Hetzner Ubuntu machine.

Install TiddlyWiki and create a server:

npm install -g tiddlywiki

tiddlywiki {server name} --init server

Create a systemctl file for Tiddlywiki, e.g. etc/systemd/system/tiddlywiki.service

Add the following for a barebones systemd service:

[Unit]
Description=TiddlyWiki Server
After=network.target
StartLimitIntervalSec=0