As part of a re-hash of my home servers and development environment, I’m focusing on containerised app/software installation in server environment. In particularly I’ll be focusing on Vagrant for the setup and configuration of quick dev environments and Docker for running software securely in it’s own containers.
Below you should find a short list of the steps required to set up a server with Docker, install Gitlab, PostgreSQL for storage, Redis for caching, and nginx as a reverse proxy to serve requests to your Gitlab instance.
I’m sorry Ops blog, I know I’ve been neglecting you lately. It’s just I haven’t had many projects recently that would fit in with this blog or be worthwhile making a post about. However that’s changed a bit since the past weekend.
Although I’ve been preparing for and busy with a new job, I found some time to develop a small journal-keeping project that I’ve aptly named re:mind Journal that’s properly available online in all it’s glory.
Okay, so Kindle For Mac is an okay program and I wanted to explore it’s reader capabilities a bit more since Calibre’s built in reader is a bit lacking in aesthetic (important when reading for long tracts) and slow to respond to user input. However I discovered something very annoying when first loading up Kindle; it only imports the books that you have purchased from Amazon, not the Send-To-Kindle documents that are also on Amazon Cloud Drive.
It’s good to be back and blogging again about potential issues or tutorials when operating or deploying equipment. In this instance, Ubuntu 14.04 with Samba fails to load nmbd on startup (at least especially when using a statically assigned IP), preventing it from starting a NetBIOS Name Server advertising it’s hostname on the local network. There is a pretty easy solution/workaround for this however, so we’ll be brief.
You need to open up /etc/init/nmbd.
A problem I’ve been having recently with a couple of Ubuntu 14.04 servers is receiving a “Waiting for network configuration” and “Waiting up to 60 seconds more for network” messages on boot, despite all network functions being available once it’s finished booting. I’ve so far tracked it down to an issue with the servers that have both static IP addresses set and Samba installed through Aptitude.
The fix I found for it is updating your /etc/network/interfaces file so that the static IP address assignment looks something like the following:
Sorry for the relatively long time without updating, I haven’t been working much on the Operations side, either confidential programming or relaxing (quite substantially too).
So I noticed my Samsung Galaxy S III had been becoming quite sluggish as of late and even a factory reset and reconfigure didn’t seem to fix things, so I decided to finally look at flashing another rom and went with CyanogenMod.
My choice was mainly based on popularity having heard it mentioned the most (in good terms) and with it’s positive reputation and light footprint I was easily swayed (I’m using past tense but am writing this up as I go along).
So the reason I needed to back up one of the SD Cards from my RaspberryPi earlier (and I wrote a tutorial about it) was I wanted to explore PirateBox, a free software implementation of a private network for users to anonymously connect, chat and share files.
I utilised the tiny, 802.11n USB adaptor that I got with my RaspberryPi and a 16GB thumb drive I had lying around to build it.
Welcome again to another short Adam O’Grady tutorial! This time I’m going to run through the brief process of cloning an SD card. This is particularly useful for backing up things such as images of Raspberry Pi installs and can be extended to use with USB flash drives that are used for boot images as well (or actually most other drive types).
Disconnect the SD card you want to back up, open up a Terminal prompt and run df -h.
As mentioned previously, I’ve been interested and have started using rsync as my backup utility for backing up important files. I thought I would right an extremely brief post on some of my thoughts for setting this up. For the sake of security, I recommend backing up over SSH with the -e ssh option when backing up to remote servers, but to get this working automatically through cron you’ll also need to set up SSH access without a password for your root user.
If you have a computer with two Network Interface Cards (NICs) set up, you can set them in the middle between your gateway/router and the rest of your network, by plugging an Ethernet cable from the router to said computer, then either Ethernet from computer to rest of network or use the computer to create a wireless network (with tools such as hostapd) which other clients can connect to. We don’t aim to cover this in particular, however we will give a good setup you can use if you’re router is running DD-WRT (a feature-packed distro for Linux-based consumer routers).