benawad/dogehouse

★ 9,032TypeScriptAudience · developerComplexity · 4/5Setup · hard

Mindmap

mindmap
  root((DogeHouse))
    What it does
      Voice audio rooms
      Social platform
      Open source Clubhouse
    Monorepo Components
      Elixir API backend
      Next.js web app
      React Native mobile
    Desktop
      Electron wrapper
      Homebrew AUR Snap
    Architecture
      Shared API client
      Staging prod branches
    Audience
      Fullstack developers
      Open source learners

mindmap root((DogeHouse)) What it does Voice audio rooms Social platform Open source Clubhouse Monorepo Components Elixir API backend Next.js web app React Native mobile Desktop Electron wrapper Homebrew AUR Snap Architecture Shared API client Staging prod branches Audience Fullstack developers Open source learners

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Study the Elixir backend architecture of a real-time audio room application to learn how to build WebSocket-heavy services

USE CASE 2

Use the monorepo structure as a reference for sharing an API client library between a web app and a React Native mobile client

USE CASE 3

Fork the Next.js frontend as a starting point for building a live-audio or social platform web interface

USE CASE 4

Learn how to package an existing Next.js web app as a desktop application using the Electron wrapper and distribute it via Homebrew, AUR, and Snap

Tech stack

TypeScriptElixirNext.jsReact NativeElectron

Getting it running

Difficulty · hard Time to first run · 1day+

Requires setting up multiple services including Elixir, the voice infrastructure, and web or mobile frontends, this is an archived project with no active maintenance.

In plain English

DogeHouse was an open-source voice conversation platform where users could join audio rooms and talk with others, similar in concept to Clubhouse or Twitter Spaces. It was built and open-sourced by developer Ben Awad and attracted community contributions during its active period. The repository is organized as a monorepo with several distinct components. The backend API, called kousa, is written in Elixir. A separate service called shawarma handles the voice audio infrastructure. The web frontend, kibbeh, is built with Next.js. A React Native mobile app called pilaf handles mobile clients. An Electron desktop wrapper called baklava packages the web app for Windows, macOS, and Linux. A shared API client library called kebab connects the pieces. The desktop application was distributed through multiple channels: direct downloads from GitHub Releases, a Homebrew tap for macOS, an AUR package for Arch Linux, an official Debian APT repository, and a Snap package for systemd-based Linux distributions. After installing the snap, users needed to separately grant microphone access via a snap connect command. Development contributions were directed to a branch called staging, with a separate production branch tracking what was live at dogehouse.tv. The README encourages contributors to open an issue or comment before starting work to avoid parallel efforts on the same change. The README is brief and does not describe the platform's feature set in detail beyond its core audio room concept. It links to a separate documentation repository, a Discord community, and a short explainer video by the creator describing why the project was built.

Copy-paste prompts

Prompt 1

Walk me through the DogeHouse monorepo structure, what does each package (kousa, shawarma, kibbeh, pilaf, baklava, kebab) do and how do they connect to each other?

Prompt 2

Show me how the DogeHouse Elixir backend handles real-time WebSocket connections for an audio room with multiple participants joining and leaving.

Prompt 3

I want to build a Clubhouse-style voice room web app. What can I learn from the DogeHouse Next.js frontend about managing audio state and live room membership?

Prompt 4

How did DogeHouse distribute its Electron desktop app across Homebrew, AUR, Debian APT, and Snap at the same time? Show me the general multi-channel distribution approach.

Open on GitHub → Explain another repo

← benawad on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.