I've been a fan of Minecraft for some time now and I've had a copy of Minecraft: Pocket Edition for at least a year. While I still find it a fair amount more difficult to play over it's Xbox One and Xbox 360 counterparts, I do still find it enjoyable to pick up and play here and there.

With the announcement of Minecraft Realms, I thought it wouldbe neat to give that a go with a friend, especially since he got himself a new iPad as of recent. However after reading through their EULA I was completely put off. I did a little looking around and came across PocketMine. It's a solution that allows you to host your own Minecraft server, specifically for Pocket Minecraft. Of note, you can't run the normal version of the Minecraft server as that will only work for the PC/Mac versions of Minecraft.

I orginally started setting up my server environment on a CentOS 6.7 server however after messing around with trying to get an updated version of glibc to work on the system, I gave up and installed Ubuntu 14.04. During the installation process of Ubuntu I setup a user account, minecraft.

Logged in as my minecraft user, I created a new directory in it's home folder called server. I like to keep everything as organized as possible. Change into that directory:

cd /home/minecraft/server

Once in that directory run the following command. This will download and run the PocketMine installer:

curl -sL https://raw.githubusercontent.com/PocketMine/php-build-scripts/master/installer.sh | bash -s -

Hopefully everything goes without a hitch. It should not only fetch the server itself but install PHP 7.x (at the time of writing this was the version it got).

Next run ./start.sh and it'll bring you through an initial set of questions. Most of them are pretty self explanatory. Once that is done your server should be online.

On your mobile device, go to Play and then hit the Friends tab. If you're local to your server (as in on the same network) you should see your server as already being in the list. If you're not local to server, such as your friend who's at their house or if you're connecting when you're on the go, then you'll have to manually add your server. By default the PocketMine server runs on port 19132, which should be the default value in your Pocket Minecraft.

All in all, it probably took 20-30 minutes to get my own Pocket Minecraft server up and running. I now have my own safe place to build and explore with my friends!

World of Warcraft - Classic

World of Warcraft - Classic

Oh man, classic World of Warcraft is awesome. I love having the hardware and knowledge to run fun projects like this.

This is perhaps the only reason I purchased a Wii U when they originally came out. I cannot wait to get my hands on this game. It's going to be fantastic.

These videos continue to impress me. How awesome would it be to see The Ocarina of Time be redone in completely in Unreal Engine 4?!

The Division Beta - vtequine

I've been having an awesome time playing through the beta for The Division over the last couple days. The beta is much better and much more refined and polished then the alpha. I have managed to actually complete missions on my own, match making and teaming up with other players is also much easier. I also made my way into the Dark Zone and have gotten some new weapons and gear. One thing I do wish was that there were a few more missions outside of the Dark Zone.

I am definitely looking forward to the final version of The Division come March 8th. I've put in my pre-order for the Gold Edition which includes a season pass and some other fun goodies. I hope everyone enjoyed playing through the beta, there's only about 18 hours left so I'll probably log a few more hours! 🎮

This is definitely the funniest thing I've seen in a while. 😝 😝 😝

Had a great time playing through this game. Who doesn't love horseback riding and space shuttles!?

Attack on Titan - Live Action Movie

I cannot wait for the second half of this movie to come out... 😍 😍 😍

Horseback riding

Houston Traffic

Now why can't traffic be like this all the time! 😝

I've been working hard to roll out the next version of my video game website, MyVideoGameList.com and today I finally pushed it out to the live site. I had some trouble with the Bootstrap date picker scripts, but I finally got them working. I was pretty much dreading working on the site because I know so very little Javascript. I probably could have rolled out the site about a month ago if I wasn't being such a big baby about this small piece of the site.

Anyways, here's some screenshots!

Destiny - Game Profile

This is what the game profile page looks like. I also got the Recently Completed By and Recently Favorited By blocks working a lot better. The rows and columns of the userpics display much better now.

jimmy's Profile

morgan's Profile

These are a couple examples of how user profiles look now. As you can see we now support a cover picture.

There's still a lot more we want to do we user profiles and the site. Items that I would love to get working this coming year would be:

  • Allow users to select and show the consoles they own on their profile
  • Show break downs of the types of genres and consoles users play on
  • Have some sort of friend feed
  • Allow users to setup and manage gaming groups
  • Possibly setup some sort of private messaging system
  • Review all the code again and make sure it's clean and tidy

Overall though I am definitely much happier with the site now. The only other thing we definitely need to be working on it getting all the games requested by users into the database. I think we have some 3500 pending requests at this point.

JSBin - Self Hosted

I've just started using this powerful tool. It also happens that it can be self-hosted which I am huge advocate for in any web software. I generally use it to tinker around with HTML and CSS as I'm not that good with Javascript but I could definitely see it being useful when I learn more about that language.

Now I just need to keep looking for a self-hosted solution that allows for real-time collaborative code sharing. And not a full on IDE, just something with nice syntax highlighting for multiple languages that lets me work on code in real time with a friend or co-worker.

My JSBin Instance.

StackEdit Self-Hosted

I recently brought on a new team member for one of my many projects. We had an immediate need for documentation collaboration. My first idea was to use Hackpad or Etherpad, but we were going to be working a lot with Markdown, so I Google'd around a bit and came across StackEdit!

As with most of our tools we use, I prefer self-hosted solutions more often then not. Thankfully StackEdit fit that bill.

My StackEdit system is a 4 virtual-core, 6GBs of RAM with CentOS 6.x VPS.

Install Prerequisites

yum -y install nano gcc gcc-c++ git

Install Node, Gulp & Bower

StackEdit runs off Node so we'll need to get that installed along with a few other npm packages.

cd /usr/src
wget http://nodejs.org/dist/v0.10.30/node-v0.10.30.tar.gz
tar zxvf node-v0.10.30.tar.gz 
cd node-v0.10.30
make install

Next Gulp:

npm install --global gulp

And finally Bower:

npm install -g bower

The StackEdit Source Code

This one is pretty quick and easy!

cd /opt/
git clone https://github.com/benweet/stackedit.git

Now we need to install some of it's dependencies.

npm install
bower install --allow-root

Of note, if you're not running these commands as root you may omit the --allow-root from the Bower command.

CouchDB - For Lazy Couch Potatoes!

Alright! So StackEdit will work now, however if you want to allow the synchronizing and sharing of files between people, you'll want to either setup Google Drive, Dropbox or CouchDB. I didn't have the time to setup Google Drive or Dropbox so I went to CouchDB. In fact anyone who uses StackEdit or your StackEdit instance can setup CouchDB to use with StackEdit.

I really recommend reading this documentation on how to setup CouchDB, but I'll give a brief overview here.

First go to SmileUpps. They offer free CouchDB hosting. Sign yourself up for an account. Then you'll want to setup a domain for your project.

Next you'll want to go into the CouchDB configuration to set a few items up.

CouchDB - SmileUpps

Click on the Configuration option from the right sidebar. You should see a new page with a table of configuration options. Scroll to the bottom and click on the 'Add a New Section' link and a little dialog box pops up. Enter in 'httpd' to the first field, 'enable_cors' to the second field and 'true' to the third field. Don't use the quotes of course though. Hit the Create button.


Again, go to 'Add a New Section' and enter in 'cors' for the first field, 'origins' for the second field and 'http://localhost, https://yourdomain.com' for the third field.

Now back on your server you'll want to run the following commands:

curl -X PUT https://yourinstance.smileupps.com/documents
curl -O https://raw.githubusercontent.com/benweet/stackedit/master/couchdb/setup.js
node setup.js https://yourinstance.smileupps.com/documents

That should be all you need to get CouchDB going. I also recommend going to your StackEdit instance and update the CouchDB URL. Go to Menu > Settings > Advanced -- and set the CouchDB URL.

Finish Up!

Your StackEdit instance should be ready to roll. You can configure other items in the `` file.

One thing I had an issue was when sharing documents was that it kept using the stacked.io domain which would likely cause some confusion. So in order to remedy this I had to edit the ./public/res-min/main.js file in 2 places. The first is line 13692:

var l = "http://mydomain.com/" + "editor#!" + e.param(a);

and line 13703:

var l = "http://mydomain.com/" + "viewer#!" + e.param(a);

I restarted the application and all was well!


  1. My instance currently is not connected with any of the third party apps like Dropbox, Google Drive or Google Analysts. I do not believe it would be terribly difficult to set these items up but I just didn't have a time or a real need.
  2. This is one of the first self hosted apps which I haven't had to proxy with Nginx. That's nice!
  3. I am not sure if the app should be running as root or a less privileged account.
  4. I also removed the donation links and alert boxes since I had no real use for them on my internal site.
  5. I also removed the link to Classeur since I had no real use for that being there.
  6. I also noticed it looks like you can deploy your StackEdit instance to Heroku or Docker, but didn't give those a shot. Maybe someday!

StackEdit Self-Hosted