In the previous post, I introduced the basic structure of the Cinode Maps Helm chart. This resulted in a simple PostgreSQL installation with default settings. Before it can support Cinode Maps, however, the setup requires slight tweaking. Let me guide you through the changes I made. The source of information The original Cinode Maps generator was built using the overv/openstreetmap-tile-server Docker image. It is a perfect solution to quickly spawn a custom map tiles server as a single “batteries-included” Docker container.

It’s been a while since I published my last post, but it’s time to start writing again. There are many topics about Cinode internals that I’d like to cover but before I do another deep-dive post about cryptography I’d like to start with another topic - Cinode maps. This post starts a series of blog posts about my recent adventures with Cinode maps. Despite some personal challenges I faced in 2024, I was still able to push this project forward a little bit.

Remember Cinobelix, the big guy with an insatiable hunger for data? Let’s kick off this year’s stories with one of his adventures. This isn’t just the first post of the new year; it’s also the inaugural entry in a series where I’ll demonstrate practical examples of working with CinodeFS. Key holder Cinobelix is holding the keys to the Cinode Maps project. Not in the sense that we, humans, tend to use our keys.

Today, I’d like to focus on Cinode’s filesystem layer. This layer transforms binary data blobs into a manageable format, greatly simplifying data interaction from an application perspective. Taking this blog as an example: it is served through a dedicated proxy exposing a complex blob-based dataset in a nice structure of directories and files that every browser understands. Until now, the toolbox for building filesystem data in Cinode has been somewhat limited.

This is the second post in the series of dynamic links anatomy. Last time I described the public layer of dynamic links. Now it’s time to dive into the private one. As a quick recap - the public layer prevents propagation of incorrect data by performing cryptographic validation but is only allowed to work on the encrypted dataset. The private layer on the other hand works on the decrypted data relying on the validation that was already made on the public layer.