Heroku pipelines

After an incident this morning when I did a

 git push staging  

instead of a

 git push development  

I decided it was time to look in more depth at the heroku pipelines lab feature, and after a quick look I am very pleased I did. It allows me to just have one heroku remote which I have at the bottom of the pipeline, with staging and (eventually) production further downstream. When we are ready to release to the client for user acceptance testing then we can simply call:

 heroku pipeline:promote  

which sends the development version to staging. No need to retain separate development and staging branches in git now, we can just have the one which we promote.

Bootstrap dropdowns with checkboxes

I needed to put some checkboxes in a dropdown (we're using Bootstrap so I based it on that) but I didn't want it to close when one was clicked and I wanted the button to update to reflect the values given so I came up with the following:



Works nicely!

Chrome preloading webpages

I am probably very late to this particular party, but I just noticed that as I typed in my local web server address into Chrome that a hit was appearing on my web server before I clicked enter, and before any content was loaded onto my screen. It appears that this is a setting in Chrome (Settings > Advanced settings > Predict network actions to improve page load performance).

I was very impressed, but I did wonder if it might have some effect on analytics if the user starts typing in an address but changes their mind - does it run javascript on the page prior to load? Can analytics tell if it is a pre-render or a full render?