I’ve been doing a bit of spring cleaning to the Known repo, removing unnecessary files, tidying up various bits and bobs. One thing I did, because it actually made some client work testing easier, was to move the Known vagrant wrapper into its own repo.

This makes the wrapper much easier to maintain and deploy (for me at least). I also took the liberty of tidying up a number of issues with the ansible configuration which was preventing the provisioning script from working properly.

Usage

You need to download and install a number of tools first, namely: VirtualBox, Vagrant, and Ansible.

Next, you need to check out a copy of the Known repo (or your Known based product environment) into a sub directory called Known. Symlinks should also work.

Run vagrant, and your new Known install will be provisioned as withknown on 192.168.33.33, I recommend modifying your /etc/hosts file to alias this.

Hope you find this useful!

» Visit the project on Github...



Vagrant logo by Fco.pljOwn work, CC BY-SA 3.0, Link

One of the deprecated features of Known is video support. This was build in to the Audio plugin back when it was the Media plugin, but it didn’t really work very well.

The missing component was video transcoding – converting the uploaded video into something that can be played in the browser. This plugin attempts to fill that hole…

Installation

  • Drop VideoTranscode into your IdnoPlugins directory and activate
  • Install ffmpeg sudo apt-get install ffmpeg x264
  • Configure the location of ffmpeg and qt-faststart

Now, when you upload a video, it will be queued and transcoded.

It is strongly recommended that you use the Asynchronous Queue in your Known configuration as this will do the transcoding in the background.

You should also run the service queue as the web server user, so that it can read and write files, e.g.

» Visit the project on Github...

A few months ago I wrote a bit about extending your Known plugins to support console functionality. I’ve recently pushed a patch which will make this functionality even more useful.

Previously, you could only have one console command available to your regular Known plugin, this was of course limiting. Now, you can have multiple!

Create a directory Console within your plugin’s home directory. Then fill it with one or more classes, which extend \Idno\Common\ConsolePlugin, one for each command you want to export. The format of this is exactly the same as those for any other console plugin.

Enjoy!