This weekend that just passed, I just moved this off a bloated reseller server and onto Digital Ocean, added SSL and Jetpack for CDN.
All the old posts are private. Mostly because they’re old, embarrassing and I really needed spellcheckers. I don’t know what I’d do without the help of robots.
I use this site to experiment with WordPress, tinker with (mostly) PHP code, optimize my server and other marketing-type things. I’m hosted on Digital Ocean because it’s cheap for a small site.
Here are some of the other marketing things I do on here:
- experiment with:
- traffic to this site (purchased or organic)
- test the user experience (a/b, mvt, and personalization)
- enhance various site attributes
You may be lucky to find something interesting here, but probably not. This is a totally selfish and self-serving site.
An error occurred while installing nokogiri (220.127.116.11), and Bundler cannot continue.
Make sure that `gem install nokogiri -v ‘18.104.22.168’` succeeds before bundling.
Well, this was a pain. I tried a lot of solutions such as;
rvm use system
rvm use 2.2.3 –default
Then a bunch of stack exchange solutions. But none of the solutions worked.
What did work
Simple… I got the idea from using the system’s installed version of ruby, but anyhow, since I wasn’t getting other weird El Capitan related errors, I did this, voila:
bundle config build.nokogiri –use-system-libraries
After returning from #Frosmox15 I decided to test hotjar, which claims to be “All-in-one Analytics and Feedback”.
I’ve set it up on my site and so far I’ve peeked at these features:
- heat mapping
So far it’s impressive given that it’s also free. Yet to try these features:
When setting up a webserver on a Raspberry Pi v.2, running Raspian OS, you can choose Apache or go for something a little lighter. If you follow the instructions from the Raspberry Pi website you will encounter a Cherokee installation error.
I haven’t found anything that is light and will work on Raspian except Cherokee.
I encountered a Cherokee installation error and I had a few other issues installing it. If you read the documentation on Raspberrypi.org you will find some “solutions” that just don’t work.
If you follow the instructions there, you will end up (at some point) getting this Cherokee installation error:
pi@raspberrypi ~ $ sudo apt-get install cherokee
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package cherokee is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or is only available from another source
E: Package ‘cherokee’ has no installation candidate
How to fix the Cherokee installation error
The only way I found out how to do it is as follows, get “autoconf”, “automake” and “libtool”:
sudo apt-get install autoconf automake libtool
sudo apt-get install git
Check out Cherokee from Github:
git clone –recursive http://github.com/cherokee/webserver.git
The change directory to the webserver directory you just downloaded:
Run this script
If it tells you there is no file or directory (/usr/bin/env: python2: No such file or directory)
sudo ln -s /usr/bin/python2.7 /usr/bin/python2
Then run the autogen.sh script again. Then run “make” and “make install”.
Let me know how it goes.
British Colombia residents have been waiting for the big quake that is destined to rock the west coast, but today on Vancouver Island they felt a 6.7 quake at 12.41pm (6 minutes ago from when I typed this!) Don’t fret, the Vancouver Island Earthquake happened, and the island is still there!
The good news is that there is no major damage reported from the Vancouver Island Earthquake, but not only that, smaller quakes in the vicinity of the west coast are in fact a good thing. It means the tectonic pressure is being released and in fact can prevent a large earthquake happening in the future. Alas, it could also mean that there may be more earthquakes coming.
Vancouver Island Earthquake 1946
Vancouver Island has seen its share of big earthquakes. In fact, back in 1946, an earthquake measuring 7.3 was recorded on June 23rd. Two deaths were recorded from this quake, who’s epicenter was located on the aptly named Forbidden Plateau area of central Vancouver Island, west of Courtenay and Campbell River. This quake was felt as far away as Oregon in the States.
The two deaths were from a capsizing boat and a heart attack. Vancouver Island residents were scared, and many ran out into the streets in terror. Luckily, today’s earthquake was not so fatal, and buildings seemed to hold together, unlike in 1946 when there was extensive damage to buildings, such as the Bank of Montreal building (below).
1946 Earthquake damage on Vancouver Island
Many people were concerned that Vancouver Island might break off and sink, but today’s quake just proves how ridiculous that idea is. In a really big earthquake, it is quite possible that the seafloor that is just offshore from the island may be lifted up and it is possible that the coastal area could sink, and at the worst, the sinking would be only a few meters. Residents living at the beach may experience some flooding, but the likelihood of the island crumbling into the sea is not very likely at all. Landslides in the ocean itself are possible which may cause smaller scale tsunami type effects which may contribute to localized flooding.
A relatively small Vancouver Island earthquake
All in all, a relatively small quake similar to the ones we feel here in Central America and no reports of major damage or loss of life.
Orange Donglebangs are not at all useful but since I need a phrase to test out some PPC (Adwords) stuff, they are really useful.
Now Google, be so kind as to index this please, kthxbai.
Update a minute later – thanks Google, you indexed this in about 30 seconds.
And a few minutes later we get a full post index and an advert:
I tried to make this title like snakes on a plane on ventrilo on a mac.
After 20 minutes of chatting while playing WOW I get the “ROBOT!!!” exclamation from everyone on vent, or, “Dude, just don’t talk”. Either way, here is a complete fix:
You need to replace the KEXT file AppleUSBAudio.kext with an older version. You do all this via “su” or logged in as root.
Here’s how to do it (re-written from here):
- Download the AppleUSBAudio.kext from 10.5.6 here.
- Unzip it.
- Open up terminal
- Make a backup of the existing driver by running the following in terminal
[cci lang=”bash”]cp -Rp /System/Library/Extensions/AppleUSBAudio.kext ~/Documents/AppleUSBAudio.kext-BACKUP[/cci]
- Exit any applications that are using a USB audio device and unplug all USB audio devices. In my opinion, print this page and restart your computer and ONLY open terminal. Unplug your headset please.
- Unload the existing AppleUSBAudio driver from the kernel by running the below command in terminal.
[cci lang=”bash”]sudo kextunload /System/Library/Extensions/AppleUSBAudio.kext[/cci]
If you get an error saying ” not found for unload request” your fine. If you get an error claiming it can’t be unloaded because its in use (don’t have the text in front of me) then stop and go back to step 5.
- Remove the existing driver by running the following in terminal.
[cci lang=”bash”]sudo rm -rf /System/Library/Extensions/AppleUSBAudio.kext[/cci]
- [cci lang=”bash”]sudo mv ~/Downloads/AppleUSBAudio.kext /System/Library/Extensions/AppleUSBAudio.kext[/cci]
- Remove quarantine (OSX Snow Leopard and Leopard):
[cci lang=”bash”]xattr -d com.apple.quarantine AppleUSBAudio.kext[/cci]
You can see if it was quarantined by running this:
[cci lang=”bash”]xattr -l AppleUSBAudio.kext[/cci]
- Load the new driver by running the following in terminal.
[cci lang=”bash”]sudo kextload /System/Library/Extensions/AppleUSBAudio.kext[/cci]Note: At this point if you get an error like this:check the system/kernel logs for errors or try kextutil(8)Do the following:[cc lang=”bash”]
chown root:wheel /System/Library/Extensions/AppleUSBAudio.kext
chown root:wheel /System/Library/Extensions/AppleUSBAudio.kext/*
chown root:wheel /System/Library/Extensions/AppleUSBAudio.kext/*/*
chown root:wheel /System/Library/Extensions/AppleUSBAudio.kext/*/*/*
chown root:wheel /System/Library/Extensions/AppleUSBAudio.kext/*/*/*/*[/cc]
- Confirm the new driver is loaded by running the following in terminal.
[cci lang=”bash”]kextstat | grep AppleUSBAudio[/cci]The output should look like the following (the 2.5.8b13 is the important bit, some of the other numbers might be slightly different):
sh-3.2# kextstat | grep AppleUSBAudio
129 0 0x92cdc000 0x28000 0x27000 com.apple.driver.AppleUSBAudio (2.5.8b13) <99 98 36 14 8 7 5 4 3 1>