547 posts
The China edition of GitLab, operated by JiHu Information Technology (Hubei) Co. and branded "JiHu", focuses on enterprise DevOps. I was lucky enough to join the SaaS beta — here's my look at the domestic version of JiHu.
Google has long supported proactive URL submission, but it's not a point-and-click UI for ordinary users — it's an API for programmers. Plenty of webmasters aren't developers, and since Google requires ownership verification, I can't just build a UI where people paste their own private key. Instead I wrapped Google's API to make it easier to use.
Tired of domestic databases shipping no macOS installer while doing localization work? This tutorial runs Kingbase V8 R3 (a Chinese domestic database) in a Docker container on macOS, giving your MacBook a working Kingbase development environment.
This post walks through installing OpenWRT (LEDE) on x86_64 hardware — a.k.a. flashing it. x86_64 means a 64-bit x86 CPU, common in industrial PCs. Consumer wireless routers use different chips, so first check whether the chip platform supports OpenWRT, then build an image for that platform. Images are not interchangeable.
My last post covered building OpenWRT (LEDE) manually. Building yourself gives more freedom, but it means paying for a server. Is there a free one? GitHub Actions Workflows lets you compile OpenWRT (LEDE) for free, and it's fast — the default config builds in about an hour.
I bought a small industrial PC and started playing with soft routers. Here's my write-up so the next person can skip the pitfalls I hit. This post covers building OpenWRT (LEDE) yourself; follow-ups will cover automating the build with GitHub Actions Workflows and installing the x86 soft router system.
Last time we learned synchronized thread coordination, which is enough to build real things — the most classic being the producer-consumer model. One producer keeps making resources, one consumer keeps taking them, two threads simulating that relationship, like a chef and a server: the chef keeps cooking, and the server takes the dish away once it's plated.
A follow-up to my last post, "Post-Mortem: Redis on 6379 Got Hacked, Turned into a Replica and Used to Mine Monero". This one analyzes the attacker's script and reproduces how they exploited unauthorized Redis access to get a shell and mine crypto.
We use Redis at work to cache and speed up static content. Since it was a dev environment I just spun up a Redis image in Docker and skipped setting a password, figuring iptables would keep me safe. Recently it started misbehaving.
Anyone who's touched multithreading has heard the synchronized keyword. We'll start with a broken example to show what happens without it, fix it with synchronized, and then let synchronized lead us into deadlock.
