No description
Find a file
2025-12-15 06:13:52 +01:00
budibase init 2025-12-08 13:02:12 +01:00
coreinstaller init 2025-12-09 07:10:48 +01:00
devbase ... 2025-12-15 06:13:52 +01:00
docubuilder init 2025-12-08 13:02:12 +01:00
dqlite init 2025-12-08 13:02:12 +01:00
herodev init 2025-12-08 13:02:12 +01:00
heromonkey init 2025-12-08 13:02:12 +01:00
holochain init 2025-12-08 13:02:12 +01:00
n8n init 2025-12-08 13:02:12 +01:00
postgresql init 2025-12-08 13:02:12 +01:00
xcaddy init 2025-12-08 13:02:12 +01:00
README.md init 2025-12-08 13:02:12 +01:00
requirements.txt init 2025-12-08 13:02:12 +01:00

Docker installers

use of mcp

the following installs & overwrites your global MCP config, use with care

uv run ~/code/git.ourworld.tf/tfgrid_research/docker_examples/builders/howto/mcp_install.py

more info see here, its very useful to have the MCP's directly configured though

setup your dev environment

  • make sure you have local docker on OSX I use OrbStack which is a very cool one
cd ~/code/git.ourworld.tf/tfgrid_research/docker_examples/builders/herodev
./run.sh

Herodev Stack Overview

This stack (herodev) contains four running containers that together form a backend + AI service environment.

1. heroshell

  • Image: heroshell
  • Role: Init the DB and provides way how to debug and enter the env.

2. litellm

  • Image: litellm
  • Role: LLM API service.
  • Purpose:
    Runs the LiteLLM API for large language model inference or as a proxy to other LLM APIs.

3. postgres

  • Image: timescale/timescaledb:latest-pg17
  • Role: Primary database.
  • Purpose:
    PostgreSQL 17 with TimescaleDB extension for time-series data storage and querying.

4. postgrest

  • Image: postgrest/postgrest:devel
  • Role: Database-to-REST API bridge.
  • Purpose:
    Runs PostgREST, exposing your PostgreSQL database as a RESTful JSON API.