I host my site for free with Netlify, since I moved to Jekyll in 2017. Cloudflare may not be needed with Netlify's static HTML pages, if not for the DNS management and other features I wanted. However, having to host static HTML pages in one `Cloudflare` with its features, outweigh its downside.
I tried coming up with my own design and theme in the past, and all, but I quickly lost appetite with the looks of what I'm converting from design into theme code. So everything ends up unfinished. I did it several times. I gave up several times too.
After years of using Drupal 7.x on my personal website, from timothyae.com, to using a secure protocol, and to timothy.sh, I have finally decided, after serveral months of search, to move to Jekyll for my own website, just to save paid cloud servers, among others.
"The goal of user acceptance criteria is to compile a set of statements that accurately identify what your customer does/does not want when commissioning your project. Establishing user acceptance criteria is an essential technique aimed at preventing project teams going of on a tangent and building something that your customer doesn't actually want."
Ncmpcpp is an mpd client. It is compatible with mopidy and its UI is very similar to ncmpc. It's a TUI-based music player that is very lightweight. Default installation on OSX can be easily done with `brew install ncmpcpp`.
After learning yesterday that there exists a (dot) sh domain name, I had second thoughts of changing my old and existing domain name, timothyae.com, to a much shorter name, timothy.sh. I have been using timothyae.com for several years already, since 2008. Now, I just have registered timothy.sh, and configured its DNS to point to my existing Digital Ocean droplet server instance.
I use Comodo's PositiveSSL for this website, timothyae.com. However, after Let's Encrypt has been released and after I used it to 2 of my subdomains, I have finally decided to move to this open source SSL. Yesterday, I created SSL certificate for both timothyae.com and www.timothyae.com.
In article `Install mpd + ncmpcpp on OSX Yosemite`, many asked how to run mpd automatically. This isn't an issue at first, because I run mpd manually. I first suggested to include `mpd` into your shell rc file, but did not realise that it will run mpd each time a terminal is being opened, e.g., in new tab or window, thus resulting in `Address already in use` prompt, which may, if not, all the time, annoying.
Cowsay is a program which generates ASCII pictures of a cow with a message. It can also generate pictures using pre-made images of other animals, such as Tux the Penguin, the Linux mascot. While fortune is a simple program that displays a pseudorandom message from a database of quotations.
The following steps are the easiest way to install rtorrent - a console-based torrent client - on OSX Yosemite. The same may work on Mavericks and previous versions, but not personally tested. I previously installed it with the previous OS differently which I cannot recount anymore.
You may at one point deleted a vagrant directory, accidentally. Perhaps you had that project, finished, and wasn’t able to have it up for too long. This will make your vagrant virtual machine as an orphaned VM. So you went ahead and opened your vagrant’s default provider, e.g., Virtualbox, and delete these VMs. What you did not realise is that, the vagrant entry/ies is/are still there.
I had successful installation of mpd + ncmpcpp on Linux and OSX Mavericks. When I upgraded to Yosemite, I had this installed too, but on the exception that running mpd requires --no-daemon option. That was last year.
The tools listed here are the tools I personally use for development, and other matters. I have arranged them in categories, as well as provided information (when I can) as to when I started using them.
This tutorial is a personal knowledge based on compilation of several tutorials on the web that worked for me on how to install LEMP and PHPMyAdmin in Ubuntu 12.04. LEMP stands for Linux, Nginx, MySQL and PHP.
A multi-site with a domain name for each site; A multi-site with one shared core files, modules and themes; and A multi-site with separate databases for each site but with an option to share common users, sessions and user roles.