LunaticThinker.me

For a long time we avoided using Docker Toolkbox because we didn’t understand how to allow the containers created within the docker Virtual Box machine by using local host and not the virtual machine’s ip (usually 192.168.99.100).

This recently changed when one of my employees was forced to work for a while from within a client’s network, and even more, work under Windows while the application was to be accessed under network designated domains only. Long story short, the application had to be run on docker, however accessed on a domain like ‘myapp.domain.foo’, which also made it accessible not only to my developer as well as the rest of the group.

How many of you didn’t try to make a propert IDE from Atom by now. Let me tell you. From many many many many (I forgot how many) points of view, it’s one of the best text editors out there. And yes, with a little work, the right plugins and a lot of think through, it can be transformed into a proper IDE.

Not what I’m gonna talk abut today though… Gonna talk about a bugging issue, that always bothererd me because (at least in it’s early days (and I mean versions 1.5 to 1.8)) I experienced it A LOT. While not on SSD, but on old good and latent HDD, if Atom had a lot of plugins installed (let’s be serious, npm doesn’t do a great job with package management and neither does apm), from time to time, Atom was crashing. It was refusing to load properly, couldn’t index either the project nor the plugin list and had to reset it (read here how). Not saying it was Atom’s fault. I had like at least 100 plugins installed. Any of those could be the black sheep. But remember, I had Atom installed on both Win and Linux on SSDs drives, and never ever ever had this problem.

Too often now, my Atom setup fails to load giving the following message:

Not a permanent solution, but one to help you move on, is resetting the window state.

atom --clear-window-state