Aaaaaand, live again…

Unfortunately not in time for the SOTM, but as of yesterday the map is alive again and ready for some inspired hacking.

Things to learn:

  • Puppetizing 90% of my setup was crucial in getting my setup running on a new box again.
  • The missing 10% prevented a smooth restart. I might even have been able to get everything working in the morning before the first talks.
  • As with everthing in IT, getting near 100% is time-consuming as hell.
  • Backups. Backups. Backups. Can’t say how happy I was that my system were periodically backed up, including automated wordpress extracts and mysql database dumps.

Now, back to hacking on some new features 🙂

Map loading, please wait ...

Broken, just at the worst possible moment

Just as I was doing the final preparations for my travel to Brussels, and maybe presenting the mosques map to some interested parties, I discovered that the backend is broken, and maybe was even broken for many days.

Shame on me, especially because at my day job, I consult people about resilient applications and the importance of monitoring and yadda yadda yadda.

Long story short, I need to spend the night in the hotel fixing stuff, and coming up with a way to show sorry pages if this should happen again…

Again, shame on me 😥

Map loading, please wait ...

Houston, we are live… Or, rather, discovered

While thinking about what my minimum viable product would be and how much stuff I could add before having my little mapping project presentable to the general community, the nice guys at “OSM Blog” discovered my project.

I guess it might be something between my changes to the OSM wiki, creating a tiny page for the map over there, contributing taginfo metadata for my project, and a few other things, but in the end, they took the burden of decing when to do the annoucement from my shoulders.

Here is the link: Wochennotiz Nr. 299 / Karten

Thank you, guys 🙂

Map loading, please wait ...

The POIs are on OSM, not google

Malenki found an error on my javascript where the scripts would be broken if is disabled via noscript. Thanks to his good bug report with screen shots of his NoScript settings, I was able to fix the offending Javascript part.

Good thing is: Now, if one disables via NoScript, the offending base layers are not offered for selection.

Things to learn from this: Better test your website with noscript too, even if 95% of its functionality really requires Javascript. You never know where some errors might come from 🙂

Map loading, please wait ...