a-tabaza/mike

A self-hosted Mike setup that packages the service and its supporting systems into one local deployment.

Early work with one tracked thread; the last recorded push was July 18, 2026.

a-tabaza is shaping Mike for people who want to run it themselves. The fork packages the application with the services it needs for data, sign-in, file storage, and routing, so a local installation can come up as one coordinated stack.

The only identity signal available is the GitHub handle a-tabaza. The direction is clear: make Mike easier to deploy and operate outside a hosted environment. GitHub has the implementation detail for readers who want it.

What's in it

One-command local stack Brings the application and its supporting services up together for self-hosted use.
Built-in sign-in service Includes an authentication layer as part of the local deployment.
Local file storage Provides a storage service alongside the application.

Direction

infrastructure

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

📝 a-tabaza makes Mike easier to self-host 1 commit 28d ago infrastructuresecurity draft

A new local Docker setup lets teams evaluate Mike with its core services running on their own machine.

Threads of work (detailed view)

1 thread have been distilled into posts.

a-tabaza makes Mike easier to self-host

A new local Docker setup lets teams evaluate Mike with its core services running on their own machine.

infrastructuresecurity

1 commit · latest 28d ago