Files
aitbc/README-CONTAINER-DEPLOYMENT.md
oib ff5486fe08 ```
chore: refactor logging module, update genesis timestamp, remove model relationships, and reorganize routers

- Rename logging.py to logger.py and update import paths in poa.py and main.py
- Update devnet genesis timestamp to 1766828620
- Remove SQLModel Relationship declarations from Block, Transaction, and Receipt models
- Add SessionDep type alias and get_session dependency in coordinator-api deps
- Reorganize coordinator-api routers: replace explorer/registry with exchange, users, marketplace
2025-12-28 21:05:53 +01:00

1.5 KiB

AITBC Container Deployment Guide

Prerequisites

Your user needs to be in the incus group to manage containers.

Setup Steps

  1. Add your user to the incus group:
sudo usermod -aG incus $USER
  1. Log out and log back in for the group changes to take effect.

  2. Verify access:

incus list

Deploy AITBC Services

Once you have incus access, run the deployment script:

python /home/oib/windsurf/aitbc/container-deploy.py

Service URLs (after deployment)

Managing Services

Check running services in container:

incus exec aitbc -- ps aux | grep python

View logs:

incus exec aitbc -- journalctl -u aitbc-coordinator -f

Restart services:

incus exec aitbc -- pkill -f uvicorn
incus exec aitbc -- /home/oib/start_aitbc.sh

Stop all services:

incus exec aitbc -- pkill -f "uvicorn\|server.py"

Configuration Files

Services are started from /home/oib/aitbc/start_aitbc.sh inside the container.

Firewall

Make sure the following ports are open on the container host:

  • 3001 (Marketplace UI)
  • 3002 (Trade Exchange)
  • 8000 (Coordinator API)
  • 9080 (Blockchain RPC)

Public Access

To make services publicly accessible, configure your router or firewall to forward these ports to the container IP (10.1.223.93).