I’m used to working with Windows and Linux, I needed something that is cross compatible with those operating systems, I did some research on embedding asset and pinning them to one file, I had a look at a few existing solutions online, but I just didn’t like any of them, they often rely on using go generators to embed the asset, I honestly thought that approach was very sloppy.
So I decided to build an my own solution and came up with ZipFS, which happens to be based on a classic and proven Zip Archive format , I thought this was simple yet brilliant. How does it work? It’s quite simple, first you create the zip archive with all the asset in, with compression disabled and than append the content of the zip file to the end of the compiled application, which is very easy to do, all you have to do is run the follow Unix command.
$ cat asset.zip >> application
Provided you got
zipfs.InitZipFs("asset.zip") in the source code of the application.
All the asset you see on this site, for example favicons, *.css and *.js are served with ZipFS, so if you can see it, you know it’s working. I mean it’s works so well, I decided to stop using Docker containers for my web application, as ZipFS is now doing the isolation and also because Docker has issues with IPv6 at the moment.
I think it’s awesome, that I use some legacy solution to simplify the entire site to one file, therefore making deployment a breeze, oh I mean it’s very quick with SCP, so satisfying and very easy to automate.
Special thanks to Rémy Oudompheng, Mechiel Lukkien and Derek Parker, without them, I couldn’t came up with ZipFS. Of cause it’s not a new idea, it’s been done before, but still awesome!
P.S. Those PHP and Node users think I’m the crazy one!