Hi, I'm Tomasz

This post is part of a WebAssembly series focused on WASM and C++. The goal is to gain a thorough understanding of how WebAssembly works, how to use it as a compilation target for C++ code and hopefully have fun along the way. So, stick with me for this exciting journey.

Recap

In the previous post, I’ve compiled Lua interpreter to WASM using emscripten and successfully run it using node. There was a problem running the same code in the browser as blocking IO is not possible. Today I’m gonna try to address this issue and run Lua interpreter in the browser.

This post is part of a WebAssembly series focused on WASM and C++. The goal is to gain a thorough understanding of how WebAssembly works, how to use it as a compilation target for C++ code and hopefully have fun along the way. So, stick with me for this exciting journey.

Recap

In the previous instalment of this series, we’ve learned that WASI is an interface enabling exposure of system APIs to WASM modules. WASI is implemented by all relevant WASM runtimes; I’ve also provided an example of what needs to be done to implement WASI polyfills by hand and how to use more mature and complete implementation of WASI polyfills in the browser.

In this post I’m gonna discuss how to use binfmt_misc to build and run non-native docker images that you can build on your PC and deploy to your target machine like e.g. raspberry pi.

What’s binfmt_misc?

binfmt_misc stands for miscellaneous binary formats and in short, it allows to run non-native binaries (through the help of a format associated interpreter) on the host system just as they were native.

Although it is strongly criticised for its bloat, create-react-app is often a go to when starting a new React project. I like to start things from the bottom up, adding things up as I need them so, I prefer a minimalistic approach.

It’s actually very easy to setup a bare-bones React project using parcel. Here’s how to do it.

Initialise npm project

mkdir react-minimal
cd react-minimal
npm init -y
mkdir src

Some adjustments are needed to package.json. I’m gonna change the main to source, pointing to the index.html of my project. I’m gonna create an empty src/index.html for the interim.

Background

There’s git which is a CLI tool implementing git SCM which we all know and love.

Additionally, there’s libgit2 which is a reference implementation of git “standard”/“protocol”. The focus of it, is primarily to be used within applications that wish to integrate with git repositories and provide programmatic access to git facilities.

Usually, languages like Python or Go use libgit2 under the hood to implement git bindings. This is the case with e.g. pygit2 or git2go and many more.

In this post I’m gonna discuss how to generate SSL certificates for services hosted within your home network. This can be anything, your plex or jellyfin instance or any development infrastructure you might be hosting locally. Keep on reading if you’re tired of HTTP and “untrusted website” warnings from your browser.

The plan

I’m gonna use navidrome as an example for the purpose of this post. It’s a music player typically running on port 4533.

Recently I’ve converted one of my old PCs into a Proxmox server. In case you don’t know, Proxmox is essentially a virtual machines management environment. I didn’t really know if I’ll find it useful, just wanted to experiment a bit and maybe learn about terraform. Since then, I’m finding my virtual machines server quite useful. I can run my own small kubernetes cluster (k3s), docker registry, VPN gateway… all sorts of things. Basically, I can have whatever disposable infrastructure I want to test the technologies I’m interested in. So, as much as I encourage you to try Proxmox out as well, this won’t be the main topic of this post.