This one is from BlestaLabs.. that dark little corner of the office where we do R&D.

Watch the video first, and then scroll down for some details.

The video is below, as usual you can make the video full screen, and be sure to turn on your sound! (If you like music, no narration this time)

Let’s face it, we’re nerds, and we like to push the limits. We spend a lot of time making things run properly, you know, in the back-end. Nice and efficient like. So, what a better way to test Blesta v3 than on a credit card sized computer, right? So, we ordered some Raspberry Pi’s and waited 6 months for them to arrive.

I took one of them, and installed Debian Wheezy, Apache 2, PHP 5.4, and MySQL server 5.5 and slapped an alpha copy of Blesta v3 on it.

The Raspberry people were nice enough to ship ones with 512MB of RAM (upgraded from previous 256MB versions) but it’s obvious that the bottle neck with running a web server on a Pi is the ARM processor. As recommended, I installed php-apc, and that improved things noticeably along with some other tweaks. To improve things further I might try lighttpd, or another light weight web server, but overall performance is pretty good!

And there you have it, the next-gen Blesta on a Raspberry Pi. Hey, if it’ll run on a Pi with a tiny processor and an SD card for a hard drive, it’ll run on your web server.

Don’t fall for the lie, PI is better than cake anyway.. and it’s real! Some of you gamer nerds know what I’m talking about.

It’s incredible how quickly this year has gone by. It’s been productive, but I’m looking forward to what 2013 has in store. I think it’s going to be an amazing year for Blesta!

The v3 alpha is in its third release and is going great, the feedback we’re getting from developers is incredibly valuable and reassuring. We’re working towards the beta release now, resolving issues, and finishing up some critical features while pushing out regular alpha updates.

This week I wanted to show you custom client fields. Not an incredibly exciting feature, but it’s a really useful one.

1. Custom Client Fields are Client Group specific, create different fields for different groups.
2. Field labels can be language defines, so that they are available in many languages.
3. Text box, check box, drop down, and text area fields are supported.
4. Fields can be hidden from clients, or displayed as read-only to clients.
5. Fields can be required, and custom regular expressions can be used for validation.
6. Fields can optionally be encrypted in the database with 256-bit AES cipher.
7. And of course, custom client fields can be created and fetched through the API.

The video is below, as usual you can make the video full screen, and be sure to turn on your sound!

Whoa, it has been a busy week! If you didn’t hear, we released v3 alpha on Wednesday, which is a huge milestone. We’re excited and gearing up for the next phase, which I think will be a lot of fun.

Part of prepping for the alpha was building an installer and handling licensing. We opted to do a CLI installer for now, but you’ll have the option of installing via CLI or your browser at release. Once installed, the rest is handled in the browser — entering your license key and creating your first staff member.

The video is below, as usual you can make the video full screen, and be sure to turn on your sound!

When we originally introduced two factor authentication there weren’t a whole lot of options available to produce one-time-passwords. Since that time a number of applications have popped up for Andriod, Blackberry, and iOS devices. Chief among those is the Google Authenticator.

Using your Google Authenticator with Blesta is pretty straight forward, but requires a little manipulation to get the key in the correct format. Blesta expects TOTP keys to be in hexadecimal format (base16), but Google Authenticator uses base32. So we have to convert our Google Authenticator keys into hexadecimal before storing in Blesta.

There are a number of online utilities to perform this operation. Here’s one: http://www.darkfader.net/toolbox/convert/.

As an example, “PEHMPSDNLXIOG65U” (in base32) becomes “790ec7c86d5dd0e37bb4″ in hexadecimal. Simply select Time-based One Time Password as the two factor authentication method in Blesta then enter the converted (hexdecimal) value and you’re good to go.

You can download the Google Authenticator from the iOS app store, or Android Marketplace.

Packages in v3 are very similar to packages in previous versions, with a lot of additional functionality. The goal in redesigning packages for v3 was to facilitate addons, allow for quantities, provide for better organization of packages, and support specific pricing in multiple currencies (Rather than relying on currency conversion, which Blesta can do too).

A few notable items..

1. Limited quantities supported! If you only have 100 of them, when they are sold they’re gone.. no more orders can be placed.
2. Package Groups are new, Standard and Addon. Addon groups can be assigned to Standard groups, making their packages available as addons to the packages within them.
3. Addon packages are just like normal packages and can be provisioning. An addon for an “extra 10GB disk”, could make an API call to add the disk space, without any staff involvement, assuming the module supports it, of course.
4. Prices can be specified in multiple currencies. Set a 1 month term to 10 USD, and a 1 month term to 8 EUR and the client will be invoiced the price in their preferred currency, whatever that is.
5. Package emails are no longer combined with the welcome email template that contains account registration details. A package welcome email is sent out separately when the service is created, allowing for more flexibility and control over service creation emails.
6. Cancellation fees have been added, which are assessed if a service is canceled early.

The video is below, as usual you can make the video full screen, and be sure to turn on your sound!