osama-ata/mikeoss
Self-hosted deployment path for mike with Docker, Supabase, and MinIO
osama-ata/mikeoss has a single area of focus: making the legal AI platform runnable entirely on-premises via Docker. The work adds docker-compose orchestration for a full Supabase stack (Postgres 17, gotrue, PostgREST, Kong) and MinIO as the S3 backend, with multi-stage Dockerfiles for both the frontend and backend.
The most transferable output from this fork is a correctness bug fix buried in the third commit: shared-project queries against a JSONB column used the wrong serialization format, causing silent zero-row results for any user accessing a project they don't own.
What's in it
- Self-hosted deployment A docker-compose setup that brings the whole application up locally, without depending on managed cloud services.
- Open-source Supabase backend Uses the self-hostable Supabase stack - Postgres, auth, and API gateway - as the data layer.
- S3-compatible object storage via MinIO Files and uploads live in a self-hosted MinIO bucket, keeping storage in-house.
- Containerised application services Both the backend and frontend ship as their own containers, ready to run alongside the rest of the stack.
Direction
infrastructure
Activity
Threads of work (detailed view)
osama-ata packs Mike up to run entirely on your own servers
A self-hosting bundle that lets a firm stand up the whole stack in-house - and a fix for a bug that quietly broke shared projects.
Self-hosted Docker stack: Supabase + MinIO with a JSONB sharing bug fixed along the way
osama-ata adds a full self-hosted deployment path - docker-compose, Supabase stack, MinIO, multi-stage Dockerfiles - and catches a real correctness bug in the process: shared-project lookups silently return zero rows on any fork that hasn't patched the JSONB query format.