Figured I’d post a delicious Keto friendly breakfast that I made this weekend.  This was my second time using Flax meal to make a “Bun” for a sandwich.  It’s not for everyone, however if your on strict Keto its amazing.

Get your bacon ready for the oven.

Set the oven on 400, do not pre-heat, put the bacon in.

Everyone’s cooking time might vary, it can take anywhere from 12-20 min depending on how crispy you like your bacon.

While your bacon is cooking, prep the flax meal bun.

• 1/2 cup flax meal
• 1 tablespoon butter
• 1 egg 
• 1 teaspoon of aluminum free baking powder

Got original recipe from reddit (lost the thread though).

Melt the butter in a bowl in the microwave, then mix all the ingredients above in the bowl.

It should form a gooey blob, I try to shape the edges a little to give it more of a bun appearance. Then toss it in the microwave for 90 seconds.

After 90 seconds it should be done, and you can pop it out of the bowl.

This is what it looks like after cutting it in 1/2.

I tossed a little cream cheese on one side.  You can add an egg or whatever you wish at this point.

It came out pretty awesome and delicious. Flax is not for everyone, it can be a little on the dry side.  There are a ton of other recopies out there, some incorporate almond flour and ingredients I have yet to try.

Used the following as a reference, however that is geared toward Ubuntu (and most of it applies) https://github.com/gitlabhq/gitlabhq_install Depending upon your situation you may want to skip some of those steps such as installing ruby (I’m using RVM) and using apache…

If you have not done so already, su to root and add apt-get install sudo.

The documentation on that link is assuming you using ubuntu which uses the admin group for sudo access, and by default on debian it the sudo group. You can either edit the /etc/sudoers and add the admin group or just change the first step to the following:

sudo useradd -s /bin/bash -m -G sudo gitlabhq
sudo passwd gitlabhq
Follow the rest of the instructions (ignoring ruby if you have RVM installed)…

There is one little typo where the guide tells you to edit the gitlab.yml file under “Configure GitLabHQ” The correct path is:

~gitlabhq/config/gitlab.yml

In my case I wanted to use MySQL instead of SQLite, so I went ahead and edited the database.yml file to mysql… Added the mysql2 gem to the Gemfile then ran the following commands:

bundle install –without development test
bundle exec rake db:setup RAILS_ENV=production
bundle exec rake db:seed_fu RAILS_ENV=production

On my Dev server I’m running apache with passenger, so I added a new site pointing to the public directory of the gitlabhq user that was created during the process and fired up the url. Everything seems to be working fine, I’ll update this page as I get to play around a bit. So far it seems solid, comitted my first project and update.

My main reason for installing this was to avoid the costs of using one of the git hosting sites. I couldn’t see paying for it when I’d like to create a whole bunch of repositories for testing and side projects, cost wise it just didn’t make sense.

Disable root login via SSH

First things first, make sure you add a user on the Xenserver box.  This is the user you will allow to login via SSH (if you have SSH running at all).

Edit the sshd_config, and find the text #PermitRootLogin yes and change it to:

PermitRootLogin no

Right below that add a new line, and replace USERNAME with the username you created.

AllowUsers USERNAME

If you have more then one user that you want to add just put a space between them and add them in succession.  Example:

AllowUsers john harry bob

Then go ahead and restart sshd:

/etc/init.d/sshd restart

Open up a new terminal session and make sure you can login to the server under your new user, and you should be good to go!

Edit the web page that XenServer shows or limit access completely

Xenserver by default serves up a web page that gives your links to download the Xen Center admin console… The web server also servers up the XAPI that is needed for the admin console to access the server remotely. So you have a few options, edit the index.html page to remove the data on there and serve up a blank page.  Or the better option is to restrict access completely to the XAPI via the hosts file.  And the best option is to toss the Xenserver behind a firewall (hardware or software).  Perhaps I’ll go into detail on how to do that in a future post, but in short, firewall the entire server and tunnel in via SSH, which would be the most secure avenue. The only downside to restricting access via a firewall or restricting access via the hosts file is that if you are not at home / work / at a PC where you have access to the restrictions in place your, out of luck on getting access to your server.   Now keep in mind, there are alternatives for access (port knocking, ssh via another server or VM, etc)  I could go on forever, but everyones situation is different. With that said, lets go over the first two options.

To prevent XenServer from showing the default index.html page, you can either edit the actual file and change it to your liking. The file is located here:

/opt/xensource/www/index.html

For the second option, you can reference the Citrix support document here for detailed information on modifying the hosts file http://support.citrix.com/article/CTX118504, however below is essentially what you need to do.

First edit the hosts.deny file located here: /etc/hosts.deny and enter in: xapi:ALL – What this does is restrict every IP from accessing the XAPI.  Second, you’ll need to edit the hosts.allow file, which takes precedence over the hosts.deny and specify the ip adresses or range of ip addresses that you would like to allow access to the XAPI.  The hosts.allow file is located /etc/hosts.allow

Allow access to a specific ip in the hosts.allow you would put in the following replacing IPADDRESS with the ip you would like to grant access:

xapi:IPADDRESS

Example:

xapi:24.22.12.222

To allow access to a group of ip addresses, for our example, lets use 24.22. – this would allow any ip address that begins with 24.22. to access the XAPI.

Example:

xapi: 24.22.

If you happen to come across this page, what do you do to lock down your XenServer installs?  I’ll be writing a few more articles as I dive deeper into Xen and XenServer, so be sure to check back often.

When using the free edition of XenServer 6.0, you’ll want to do a few things such as enabling Auto Start / Auto Boot / Auto Power On.  For some reason this feature was removed from the “Free” version in 6.0, so lets go ahead and set this up.

First your going to want to get the UUID of the VM’s you wish to enable auto start on as well as the UUID of the pool these VM’s reside in.

To get the list of the pool’s on your XenServer type:

xe pool-list

Copy the UUID of the pool, in my case there ist just one pool. Then issue the following command, and replace the UUID with your pools UUID.

xe pool-param-set uuid=UUID other-config:auto_poweron=true

Then, at the command prompt of your XenServer type:

xe vm-list

You should get a full list of the VM’s on the server, along with their name and UUID. Copy the UUID of the VM you wish to enable autostart then issue the command below, again replacing the UUID with the UUID of the VM you wish to auto start.

xe vm-param-set uuid=UUID other-config:auto_poweron=true

And thats it, the next time you ever need to power cycle your main server, the Xen instances should power up automatically.

I’ll be adding a few more articles over the next few weeks of some other notes and tips.  Next up is adding some monitoring to your main XenServer to see whats going on with your different instances.

All cleaned up:

Bus connector fix (common problem on 2005 and 2006 Kawasaki Brute Force 750′s)

Took the wires out of this plug, stripped then soldered.

Then taped them up nice and secure…

My “spray booth”

Someone just released a gem that will analyze your code and check for “Best Practices” -  seems promising. Check it out at GitHub here: http://github.com/flyerhzm/rails_best_practices

Anyways, here are some pics.  The flash from the camera makes it seem more shiny then it actually is, I think it came out pretty good.

Here is our poor attempt at a pumpkin carving