Press CTRL-F for a search box and type in “themes”.
Look for a link to the theme.
It’s a safe bet that this site is using TwentySeventeen. But click the search arrows to verify!
In actuality, I’m using a child theme, sds_2017, but that’s obscured because I’m optimizing the HTML and CSS for the site, so a lot of stuff is hidden, aggregated, or obscured in the name of efficiency.
After 12 years of faithful service, through 3 power supplies and several disks, I have officially retired my “basement server”, mooch. Mooch was a Pentium-4 machine running CentOS 6 used to backup stuff on my real servers, as well stuff from my desktop, and to provide a common file sharing point for systems in the house.
Enter the NAS
That system has been replaced by a five year old Dell, which has been upgraded to 8 GB of memory and a pair of 4TB drives, running the NAS (Network Attached Storage) system FreeNAS. The total cost of this transformation from an old Windows desktop to a shiny storage engine was $200 for two 4GB 4TB Seagate Drives, $35 for the additional memory, and $15 to replace a failing 100 mbps switch with a new gigabit model. The FreeNas software is free.
Using FreeNAS, I’m still providing a central git repository, server backup, and in-house file sharing. FreeNAS also supports Apple’s AFP protocol, so it’s acting as a network attached Time Machine for backing up the Macs. In addition, FreeNAS supports some nice plugins including the Plex media server, so I’m now able to play all my videos and music through the Plex app on our Roku boxes.
Was it hard to set up? Not really. The second time I did it, it took maybe an hour to get the OS loaded, disks mirrored, storage containers defined, and all the other little things configured. I kicked off the tasks to transfer data to it before going to bed and by mid-afternoon the next day, about 500GB of stuff had been transferred.
That was fun… now on to the next project, either a gitlab server or replacing the toilet in the upstairs bathroom.
How do I change the font size? Why is the background blue? These are questions easily answered through the Chrome Developer Tools. Anyone wanting to do any customization of a web site needs to be familiar with them.
Updated April 30, 2017: This is the presentation given at WordCamp Chicago. Thanks to the many people who came to the presentation and offered comments and compliments!
I’ve rejiggered things. This server is no longer using mod_ruid2 (see here). I’ve switched to the more modern and maintained php-fpm process, under PHP version 7. The system seems to be faster while using less memory and CPU.
Thanks to Opsec and JPhase for assistance on this!
Plugins can do many things. Some plugins do more than one thing. Some are close to what you want done. So, first thing first. Understand clearly what you want to accomplish.
#2 Is it well supported?
Many people start by looking at a plugin’s reviews. I look at the support threads for the plugin. It tells me whether the author is engaged, active, accepting feedback, and fixing bugs.
#3 Do updates appear at regular intervals or is there long time between them?
There are good reasons why a plugin might not get updated frequently. If you see lots of issues and bugs in the support queue and infrequent updates, it gets back to whether the author is engaged.
#4 Are there enough people using it to cover “edge case” bugs?
Ideally, someone else finds a bug before you do. The more users, the wider the variety of environments the plugin lives in. Does that mean you won’t find a bug? No, but reduced the likelihood that you’ll be alone.
#5 What else have the authors done?
Does the author have other plugins? How are those supported?
I get asked that a lot. “Steve, what’s the deal with the red sneaker?” It’s a story — not a long one, but it is a story.
When I first found myself out in the job market, my wife and I took advantage of not having to go to work on weekdays to go up to the outlet mall in Pleasant Prairie, WI where, after first stopping at Culver’s for a burger, rings, and shake, we spent a few hours shopping. There was a sale at the Converse store and I bought a pair of red Chuck Taylor’s.
Fast forward to a meeting of the Executive Network Group. I felt the need to dress like a grown-up, so I put on a sport coat, but I also felt the need to act out a bit, so I wore my Chucks. I did the networking thing. At the next meeting, I wore them again and someone came up to me, telling me he had been referred by someone else in the group. He said something like “Bob didn’t remember your name, but said you’d be wearing red sneakers.” And with that, I realized that I had developed a brand!
I made a point of wearing those Chucks to every networking event, despite the fact that they’re just as uncomfortable as they were when I wore them for gym 50 years ago. People remembered me (in a good way, I think), and that’s one of the big points of networking. As I developed my website, it made sense to carry that brand onto the web, business cards, etc.
mod_ruid2 allows the web server process, httpd, to run as a different user when accessing different websites on the same server. Why is this important? By default, the web server runs as the user apache and all files are owned by the user apache. If there’s a vulnerability in one component of a web site that gives an attacker access to the server’s file system, it has access to any and all files owned by apache. And that’s all she wrote.
When using mod_ruid2, each host on the server is owned by a different user account, so any file system access is limited to just that site. It’s a way to limit the damage
Anyhow, I ran into problem. Some of my sites use session cookies. I was getting strange errors on those sites that I tracked to problems related to session cookies. On CentOS 7, session cookies are stored as files in /var/lib/php/session. That directory has permissions of 770 for the user/group root:apache. The new users assigned to the httpd process by mod_ruid2 are not able to access this directory. The solution was to create new group, webruid, and add each user that is used as a mod_ruid2 user to that group.