The new Vikings stadium is a sandcrawler

The new Vikings stadium is a sandcrawler

Is it just me or does the new Vikings stadium look like a Jawa sandcrawler from Star Wars?

Tagged ,

Change the Steam Font Size

I recently upgraded to the latest Steam beta, and discovered that Valve increased the size of the font in the chat windows. Opinions of the font change vary, but I personally can’t stand it.


Here’s how to fix it (discovered in the steam forums).

Go into your steam directory, and open

resource/styles/steam.styles

The key here to find the sections that pertain to chat windows, and change their font-size parameters to 14 (if you want the original steam font size). After making the changes, restart Steam and you’ll be good to go.

    friends_chat_text
    {
        textcolor="text"
        selectedtextcolor="TextentrySelected"
        SelectedBgColor="focus"
        font-size=14
    }

    friends_chat_text_self
    {
        textcolor="ChatOwnTextColor"
        selectedtextcolor="TextentrySelected"
        selectedbgcolor="focus"
        font-size=14
    }

    friends_chat_history
    {
        textcolor="ChatDialog.HistoryColor"
        selectedtextcolor="TextentrySelected"
        selectedbgcolor="focus"
        font-size=14
    }

    friends_chat_event
    {
        textcolor="Text"
        font-size=14
        selectedtextcolor="TextentrySelected"
        selectedbgcolor="focus"
    }

    friends_chat_bright_event
    {
        textcolor="text"
        selectedtextcolor="TextentrySelected"
        font-size=14
        font-weight=1000
    }

    friends_chat_url
    {
        textcolor="text"
           SelectedBgColor="focus"
        font-style=underline
        font-size=14
        selectedtextcolor="TextentrySelected"
        selectedbgcolor="focus"
    }

    friends_chat_name_ingame
    {
        textcolor="Friends.InGameColor"
        selectedtextcolor="TextentrySelected"
        selectedbgcolor="focus"
        font-size=14

    }

    friends_chat_self
    {
        textcolor="Friends.OnlineColor"
        selectedtextcolor="TextentrySelected"
        selectedbgcolor="focus"
        font-size=14
    }

    friends_chat_name
    {
        textcolor="Friends.OnlineColor"
        selectedtextcolor="TextentrySelected"
        selectedbgcolor="focus"
        font-size=14
    }

    friends_chat_accountid
    {
        selectedtextcolor="TextentrySelected"
        selectedbgcolor="focus"
        textcolor="text"
        font-size=14
    }

    friends_chat_securitylink
    {
        textcolor="text"
        bgcolor="none"
        font-family=basefont
        font-size=14
        font-weight=400
        font-style=underline
        selectedtextcolor="TextSelected"
        selectedbgcolor="Focus"
    }
Tagged

I’m happy to see that PuppetLabs recently released an AskBot site at ask.puppetlabs.com.  AskBot is a Q&A site ripped off from very similar to StackOverflow.  PuppetLab’s site is still in beta, but there are already several good questions being asked and answered.

Puppet questions are typically answered in IRC, or through the mailing list.  Rolling out AskBot is a welcome change that will serve to help new users, and collect answers to common questions for reference in the future.

ask.puppetlabs.com

Tagged

GTD with Mailbox and Gmail

I finally received my invitation to Mailbox today, and so far, my experience has been positive.  After quickly clearing my inbox in the mobile app, I logged into Gmail to see if I could determine what Mailbox was doing behind the scenes.

It turns out that Mailbox applies catch-all labels to messages, and then manages the specifics outside of Gmail.  For example, whether scheduling a message to be addressed later in the evening, or later in the week, Mailbox simply assigns a ‘[Mailbox]-Later’ tag.  While this is just fine when using the mobile app, it leads to problems when trying to tackle tasks through the traditional web interface.

The problem I have with Mailbox, and with most to-do apps, is that it’s hard to work them into all of my workflows.  I really like using multiple stars in Gmail, but those stars are only available in the Gmail web app.  At work, I have to use Outlook, but Outlook’s to-do system in entirely detached from my Gmail system.  When I’m in the car and I think of something I have to do, I frequently use Siri to add a task on my phone.  Suddenly, managing tasks that are located in multiple different locations becomes more work than it’s worth.

I’m going to continue using Mailbox because of the handy reminders that can be set to deal with emails in the future.  The idea of getting an email, and being able to tell my phone to remind me to tackle it later really appeals to me, mainly because I’ve never been one to remember to look at my to-do list.  I’m the type of person that keeps my to-do list on my screen at work all day, every day.

I also found a way to work Mailbox into my existing Gmail system of using multiple stars along with multiple inboxes.  My GTD system is very simple.  I use four categories: Actionable, Waiting/Delegated, Information, and Completed to categorize all of my email that can not be immediately dealt with.  My Actionable inbox uses a simple search to display only emails with a yellow star.

has:yellow-star

I expanded that search to include emails with the ‘[Mailbox]-Later’ label, so that when I’m looking at my actionable items in Gmail, I can see emails that I’ve marked for follow-up from within the Mailbox app.

has:yellow-star || label:[mailbox]-Later

It’s not fancy, and it’s certainly not verbose enough for many GTD implementations, but I’m hoping it’s just enough to let me quickly mark personal emails for follow-up, while still letting me use the Gmail web interface to see all of my emails that need to be tackled.

Tagged , ,

Puppet Enterprise and PuppetDB – Failed to submit ‘replace facts’ command

I’m working on setting up PuppetDB for the first time with a Puppet Enterprise master.  For my purposes, the PuppetDB node is a separate server from my master.

When trying to sync the agent on my master for the first time, I got an error while connecting to PuppetDB.

Jan 18 23:34:52 ubuntu puppet-agent[4023]: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for puppetclient.domain.com to PuppetDB at puppetdb.domain.com:8081: Certname "/o=*.domain.com/ou=domain control validated*.domain.com" must not contain unprintable or non-ASCII characters<br />

I tried recreating my keystore and truststore files in /etc/puppetlabs/puppetdb/ssl, but I kept getting the same error.

After some digging, I found a script: /opt/puppet/sbin/puppetdb-ssl-setup.

I tried running this script, but it kept complaining with the following error.

root@puppetclient:/opt/puppet/sbin# ./puppetdb-ssl-setup<br />cp: cannot stat `/etc/puppetlabs/puppet/ssl/private_keys/puppetclient.pem': No such file or directory

Thoroughly frustrated, I dug into the script and found the problem.

fqdn=`facter fqdn`
# use hostname if fqdn is not available
if [ ! -n "$fqdn" ] ; then
    fqdn=`facter hostname`
fi

When I had setup my puppetclient server, I didn’t bother to configure DNS.  I had created an entry for puppetdb.domain.com in /etc/hosts, and had manually specified puppetclient.domain.com in my puppet.conf file.

During the initial Puppet Enterprise setup process, /etc/puppetlabs/puppet/ssl/private_keys/puppetclient.domain.com.pem had been created, but without DNS, `facter fqdn` was returning nil, so puppetdb-ssl-setup was using `facter hostname` instead.  Since /etc/puppetlabs/puppet/ssl/private_keys/puppetclient.pem didn’t exist, the script failed.

After configuring DNS, `facter fqdn` correctly returned puppetclient.domain.com, and puppetdb-ssl-setup completed successfully, allowing my puppet agent to successfully connect to puppetdb on sync.

The initial problem seems to be a bug with the way the puppet agent handles the certificate validation.  I was not able to use a keystore.jks file made from a valid cert from Thawte, but using puppetdb-ssl-setup proved to be an effective way to get things moving.

Of course, I found these sites after I had solved the issue.
http://serverfault.com/questions/400092/puppetdb-failed-to-submit-replace-facts-command
http://projects.puppetlabs.com/issues/14837

Tagged ,

Highlighting source code on wordpress.com hosted sites

I’ve never hosted a blog on wordpress.com. While I’m enjoying the “freeness” of the site, I’m struggling with not being able to edit themes and install plugins.

At first I was worried that without plugins I wouldn’t be able to highlight source code. After some digging, I was fortunately able to find a couple of different ways to do code highlighting.

Use the WordPress built-in shortcode

The simplest way to highlight source code on a hosted WordPress site is to use the built-in sourcecode shortcode.

The following markup

[sourcecode language="html"]
<div>
    <h1>Hello, World!</h1>
</div>
[/sourcecode]

produces

<div>
    <h1>Hello, World!</h1>
</div>

There are a lot of great parameters that can be used to configure the code box features which include highlighting specific lines, controlling the line wrapping, and collapsing the code box on page load, to name a few.

Embedding GitHub gists

Source code highlighting is great, but sometimes it’s nice to have revision history so that readers can see bug corrections.  Gists are great throw-away Git repositories that can be used for snippets and pastes.  Gists also have the added benefit of being portable.  If you ever outgrow wordpress.com, you can take your code snippets with you.

Gists are normally embedded on a site using javascript.  I was excited to try it out, but was disappointed to discover that wordpress.com does not allow inline javascript to be added to posts.  After searching a bit, I discovered that a gist shortcode was added specifically for embedding gist source code in WordPress posts.

Embedding all gist files

A gist can easily be embedded in a post using

[gist https://gist.github.com/4554439 /]

Which produces

Embedding individual files from a gist

A neat trick that isn’t listed on the WordPress gist support site is the ability to embed individual files from a gist.

If I only wanted to show index.html, I would use

[gist file="index.html"]https://gist.github.com/4554439[/gist]
Tagged ,