Building Runv.Club

In the early 1980s, some of the first pubnixes began to appear. A pubnix — short for public Unix — was exactly what the name suggests: a publicly accessible Unix server where people could log in, share resources, publish small personal pages, exchange messages, write scripts, and take part in an online community long before the modern social web existed.

These systems were usually built around a mix of shared Unix accounts, bulletin board culture, shell access, email, text files, and early online communities. They were not polished platforms in the way we think of platforms today. They were rough, personal, technical, and deeply human.

Around the same time, BBSes — Bulletin Board Systems — were shaping another side of online life. A BBS worked like a digital notice board: people dialed in, left messages, downloaded files, joined discussions, and slowly formed communities around shared interests. Looking back, it is easy to call the idea primitive. But that would be a mistake. BBSes were brilliant because they gave people a place to gather, experiment, and belong. They were small, local, imperfect networks with real personality.

That spirit is what still makes pubnixes interesting today.

I had accessed a few pubnixes in the past, although I never stayed deeply involved for long. More recently, while searching for these kinds of communities again, I came across some incredible projects still keeping the culture alive. The more I explored them, the more one question kept bothering me:

Why not build a pubnix focused on the Brazilian community?

That question became the starting point for runv.club.

The idea behind runv.club is simple: create a shared Unix environment where people can have shell accounts, publish personal pages, experiment with tools, learn by doing, and be part of a small community built around curiosity rather than algorithms. It is inspired by the old pubnix and tilde-club culture, but with a Brazilian identity and a modern operational base.

Technically, I built runv.club on top of Debian 13 and Python. The project is not a big monolithic web application. It is closer to a carefully assembled system: Python scripts, static HTML and CSS, email templates, documentation, shell tooling, SSH access, Apache, quotas, and user provisioning routines. The goal was to keep the stack understandable, auditable, and close to the Unix philosophy: small pieces, clear responsibilities, and enough simplicity that the system can be operated and improved over time.

The server side handles the practical parts of the community: receiving membership requests, reviewing them, creating Unix accounts, preparing user environments, and publishing a public member directory without exposing private operational data. The public-facing site remains lightweight and static, while the real experience happens through the shell, user home pages, and the culture that grows around them.

For me, runv.club is less about nostalgia and more about reclaiming a kind of internet that still matters: slower, stranger, more personal, and less dependent on centralized feeds. Pubnixes and BBSes showed that communities do not need to be massive to be meaningful. Sometimes all you need is a server, a login, a few curious people, and enough room for experiments to happen.