onetab saved my life and almost made me cry

A colleague of mine saw I had a bazillion tabs open and was like man you have a lot of tabs open, I was like well I don’t want to forget what I was working on when I get pulled in another direction and curiously I asked him because I was sure he had as many if not more and he said 1000 tabs. I was like how is that possible and he responded onetab. Onetab was originally meant for chrome but has been extended for firefox which is totally awesome.

The past 6 months I’ve been using it like a champ and may have passed my colleague. Well there was trouble with my latest upgrade to Fedora 21 and found out all my versions have some hardware incompatibilities on my laptop, which forced me to use Ubuntu… I know … It is actually quite nice … Anyways, I’m having to restore everything and well Firefox did not play nice even though I copied all my firefox files over and onetab was one of them.

I looked and looked and didn’t see any documentation on what to do for onetab recovery should your system bomb. Well I figured it out after some searching/troubleshooting.

step 1 navigate to

./mozilla/firefox/<some-string>/jetpack/extension@one-tab.com/simple-storage/

step 2 copy database to the same location as ^^^ on new machine

store.json

step 3 enjoy!

Advertisements

Docker and my initial thoughts

This past week I had an opportunity to tinker a bit with Docker and I think it is really cool… But I’m not sure I think it is quite the silver bullet that everyone makes it out to be.

Will Docker stream line deployments across environments, yes.

Will Docker ensure consistent configurations for the server environment, yes.

Will Docker replace Maven, no.

Will Docker replace continuous build servers, no.

Will Docker be used by the developers or administrators, unclear. If a developer is working in a somewhat loose data center, then the developer will need to document/script out the deployment steps so it can be replicated in each environment, which can be fraught with holes. Generally the developer will script out the deployments with respect to the application sever and not necessarily the os. This presents an issue, because now we are expecting developers to have a more in-depth knowledge of linux to properly understand the linux container and then the application server container on top of it.

Let’s assume the developer has an in-depth knowledge of the os and is capable of building images: networks, services, configuring the application server, etc. As a system admin, I would have to wondering, what was enabled/disabled within the docker image, is it secure, is it configured correctly and am I responsible for reviewing it? And what about for each development team? With a workload like this it sounds like a new position, which would eat into any revenue savings by switching to docker.

If system administrator is responsible for packaging application the outlook doesn’t look much better. To create Docker images well is challenging and does take some time to learn. No doubt adding this many layers to a Docker image some tuning would need to be done and the tuning wouldn’t necessarily be repeatable across teams/projects.

There is definitely a place for Docker, but I’m not sure it belongs at this phase of the development process. Docker seems to me to be better suited for the linux container, vice the linux container and the JEE container.

Or maybe it makes sense for a small company/team that has a lot of rock stars on it.

I’ll post more as I work with!