It’s been a busy few weeks:
- We launched TallyStick – a time tracking and billing tool – two weeks ago and have pushed some bug fixes and updates. So far so good!
- IXP Manager, an open source web application to assist in the management of Internet Exchange Points (IXPs) that we built over at INEX, got a complete UI refresh thanks to Twitter’s Bootstrap;
- Similarly, our open source email domain / mailbox / alias management tool called ViMbAdmin got a major version bump, lots of new features and a UI refresh also;
- We also just open sourced (BSD) our (admittedly small) Minify tool which makes minifying, bundling and versioning the manner JS and CSS files that make up websites these days a breeze. Check it out on GitHub: https://github.com/opensolutions/Minify.
Today, we’re pleased to announce the immediate availability of 2.0.6 which has a number of incremental fixes and improvements.
Just over a week ago, we released V2 of ViMbAdmin which was a complete UI refresh.
Thanks for all the feedback and bug reports since then.
Today, we’re pleased to announce the immediate availability of 2.0.6 which has a number of incremental fixes and improvements including:
- Domain is now ‘sticky’ when moving between mailboxes, aliases and logs making it much easier to browse a single domain;
- A cookie is now used to remember the page length for individual users;
- We now use grouped icons with tooltips rather than labelled buttons throughout;
- The horrible your IP address has changed message is gone.
As usual, a full change log is available here and the packaged release can be downloaded directly here.
We’ve put some time aside over the last week to do a major UI overhaul on ViMbAdmin – specifically incorporating Twitter’s superb Bootstrap framework. The before an after’s tell a lot about this.
Over a Open Solutions, we’ve put some time aside over the last week to do a major UI overhaul on ViMbAdmin – specifically incorporating Twitter’s superb Bootstrap framework. The before an after’s tell a lot about this. Here’s how it was:
And here’s the new improved look:
We’ve also closed a lot of bugs, improved the functionality and navigation and added a couple of small features.
Let us know what you think!
I have recently been converted from and SVN user to a Git user. You can read about my road to Damascus moment over in my personal blog.
As such I have converted my co-workers and we have migrated ViMbAdmin to GitHub. We feel that the project is in an early enough stage to not cause too much annoyance with the current user base. We do sincerely apologise for all and any inconvenience caused.
Do you want to continue with your SVN installation?
Feel free to svn switch your base from Google Code to the following which tracks our master (i.e. stable / production / release) branch:
Migrating to Git
Just follow the instructions at:
and skip the database setup. Just copy over your application/configs/application.ini file to the new Git clone.
Using Official Packaged Releases?
No problem – you’ll now find new versions at:
…and I’m bloody delighted.
The straw finally came when Nick forced my hand for a project we wanted to release through our work in INEX. I was pushing for Google Code but he had his heart set on GitHub. Now, in fairness, GitHub has some SVN bindings but after some research, I decided to dive right in.
Now, there’s both a steep learning curve but also a complete change of mindset required from centralised source code management (SCM) with SVN to the distributed model of Git. In the end, most projects will decide on a canonical Git repository anyway which pushes you slightly back towards centralised but there’s still a world of a difference.
So, what’s so good about Git? Well, lots. But first and foremost is it’s exceptionally powerful yet simple branching and merging that just works. And works fast – remember, with Git everything is local.
One work flow that used to kill me in SVN was that you’d be implementing feature X but someone needed bug Y fixed immediately involving some of the same code. Getting just the fix for Y in was tough and complicated. And branching in SVN isn’t quick or simple. In Git, I branch from the main development branch for every new feature, bug fix, etc and then merge what I need between them and back into develop when they’re ready to be pushed back to the agreed canonical repository.
I’ve been so impressed with Git that I’ve moved an open source project we created in Open Solutions over to Github: ViMbAdmin. I’ve also forced the rest of my team in Open Solutions over to Git and migrated a number of customer projects already. And we’re reaping productivity rewards!
How we work Git for projects was taken from this excellent post which I would fully recommend: A successful Git branching model.
Useful Git Links: