iDetailAid Blog

So, last week I was writing a post about cleaning up after docker, and I got a bit carried away and ended up deleting a data container. The container was no longer running, but it's docker volume was still in use by other running containers.

Thankfully, I didn't use the -v flag (which removes the containers volumes as well - although volumes in use wont get removed), so I still had all the data, I just had lost the container that created it.

The problem is, docker references the volume via the container when mounting it as a shared volume. As I had deleted the container, I could no longer reference the volume.

Thankfully there is a very simple solution to get the volume mapped back to the data container.

We have some ansible scripts that deploy docker containers on to various environments. All has been going fine until this week, when we fell foul of the untidy teenager that is docker!

Our deployment was failing as the box had run out of disk space. Turns out you need to tidy up after docker...

New partnership provides a quick and easy way to create, update and localise compliant eDetail content within Veeva’s best-in-class document management and control solution

Veeva Systems Inc., a leader in cloud-based software for the global life sciences industry, has today welcomed iDetailAid as its only Veeva Approved eDetail content authoring platform. The partnership will compliment Veeva System’s end-to-end service capabilities to deliver increased functionality for its customers.

We are delighted to announce the release of iDetailAid 1.6.0 which will be available on Thursday 22nd October 2015

This is a major release of the platform and it's focus has been predominantly around the slide editor and increasing flexibility and efficiency for content authors.

Sometimes EB fails to deploy and times out with a generic error:

Unsuccessful command execution on instance id(s) 'i-********'. Aborting the operation.

As of yet there is no clean way to get out of this, but here are the top 3 ways that we have got it to work - depending on your needs...

OSX quick look is great, but it only supports a limited number of text files.

We often get an issue with our MEAN vagrant dev environments where a previously working server will fail to connect to the mongo db the next time a developer does vagrant up

We use PhantomJS to auto generate images of user generated content. All was fine, until we entered the Asian markets.
It was not the usual black squares issue that you can get with Phantom, it just had spaces where the Korean characters should have been.

The font itself was loading fine, as Latin characters were in the correct type face.

After following lots of posts about installing font support packs on linux, and non of them working, I finally got it running on Centos with groupinstall for yum

sudo yum groupinstall "Korean Support" "Chinese Support" "Japanese Support"

Out the box iTerm2 and oh-my-zsh make using the terminal a whole lot easier, but there is one thing that has always annoyed me - not being to move the cursor to the prev / next words whilst entering long commands, until now...

Had a very odd issue with CSS files being loaded, but the css not being applied (and any @imports not loading either).