In my previous post, I talked about how you can use zram to squeeze more memory out of your Raspberry Pi at no cost. In this, I will talk about how you can then use that additional compressed memory to extend the life of the SD card on your Raspberry Pi.
Since the advent of the Raspberry Pi, almost all single-board computers (SBCs) on the market have followed their lead in using SD cards as the main storage medium for the OS.
The main benefits of doing so, as I see it, are:
Raspberry Pi and other single-board computers (SBCs) have always had minimal memory. At a maximum of 1GB in the Raspberry Pi 3, it was just sufficient to run lightweight programs and scripts. That trend held until the advent of the Raspberry Pi 4 with 2GB, 4GB and a few months later, 8GB models, opening doors to running databases and other memory-intensive applications.
This shift is due in no small part to the explosive growth of the data industry, where previously the focus of SBCs was IoT and embedded applications and now the focus is slowly shifting towards data applications. …
In 2018, I had the privilege of meeting a friend Lester who gave me his Pebble Time Steel as he has since moved on to Apple Watch. Two years in, this same watch I received is still serving me well, even in Singapore’s COVID-19 circuit breaker.
As Pebble web services shut down 4 years ago in 2016, I’ve switched the boot URL to point to Rebble web services instead, breathing new life into this watch.
For those who’re unfamiliar, SafeEntry is Singapore’s national digital check-in system that logs the identity and mobile numbers of individuals visiting places of interest (POI).
Those information along with the timestamp of visit would then be used for contact-tracing for prompt testing and quarantine should there be a risk of infection due to the presence of an infected individual at the same place and time. …
The Kubernetes Dashboard is essentially a web UI for managing the Kubernetes cluster that it is deployed on. It allows the administrator to perform CRUD (Create, Read, Update, Delete) operations on the most commonly used cluster resources.
Less commonly used resources such as LimitRange and HorizontalPodAutoscaler, you’ll still have to fallback to the command line to manage them. In the screenshot you can already see all the resources you can manage within the UI in the sidebar on the left.
The dashboard has just reached 2.0.0 a few months back after staying in 2.0.0-beta for almost a year. Though there still are some rough edges that can be ironed out, I feel it is sufficiently stable for production usage. …
Kubernetes or k8s in short (first and last letters, with 8 letters in-between), is all the hype in 2020 in the container orchestration space.
If you have been living under a rock in the container orchestration space, here’s what Kubernetes is:
Kubernetes is an open source container orchestration system for automating application deployment, scaling and management. It was originally designed by Google and is now maintained by the Cloud Native Computing Foundation. (Wikipedia)
In plain English, Kubernetes is a system that runs on a cluster, and provides a framework through which the user deploys applications. Kubernetes provides useful features that make deploying high-availability apps much easier, such as multiple replicas of the same app, support for load-balancers natively as well as horizontal and vertical autoscaling. …
In my previous post, I detailed my struggles with bare-metal setups of applications and how Docker saved me from the pain of installing and configuring PHP. In this post, I shall outline the process through which I (finally) started clustering.
I assume that you already have knowledge on and some experience with Docker and docker-compose. If you don’t, I’d suggest referring to my previous post which should give you some context.
Even though docker-compose was great, there was still one problem.
Docker-compose runs all the services defined on a single machine.
There’s no point to the cluster I built if everything ends up running on a single machine is there? …
I’ve been lurking around in r/selfhosted for about a year now, spying on the apps that people self-host, and their pretty dashboards full of self-hosted apps. Over time I observed some dissent in the community. There exists a group of people that vehemently reject the use of Docker.
…what happens if the container is not maintained further? i have no desire to do that. I still prefer to install my dependencies, run the applications via systemd and set up an nginx reverse proxy. i still feel like i can interact with the process. (Reddit)
I’m a person who has never really been too fond of Docker. I like having full control of the applications I’m running, their configuration and their storage. With Docker, I’ve always felt like I’ve lost a bit of that control. …