codeforpdx / codeforpdx/tenantfirstaid

improve local testing and deployments with docker containers

Open
#253 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue help wanted infrastructure
Dominant language
Python
Stars
13
Forks
21
Avg merge
6d 7h
Merged PRs (30d)
3

Description

Requirements:

  • support Mac, Linux and Windows development environments
    • support VS Code IDE
  • support Linux (Ubuntu) deployment to Digital Ocean, Google Cloud or LangSmith

Optional:

  • on MacOS >= 26.0 (aka Tahoe) support Apple Containers (though without a compose solution)

It would be good to containerize the frontend and backend separately and manage them with a docker-compose.yml.

There should be a GitHub Action that builds x86 and arm64 docker images for deployment (triggered by merge to main or manual trigger on branch).

  • The build should accept build time variables (e.g. TYPE=dev, TYPE=deploy) where
    • the dev TYPE installs dev tools for running tests, evaluations, etc.
    • the deploy TYPE should be a minimal image (strips out tests and utility scripts)
  • Built images should be uploaded to ghcr.io
  • The deployment should accept runtime variables and secrets (e.g. SHOW_MODEL_THINKING, MODEL_NAME, GOOGLE_APPLICATION_CREDENTIAL, LOG_LEVEL).

README.md, ARCHITECTURE.md & CLAUDE.md should be updated

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading README.md, ARCHITECTURE.md, and CLAUDE.md to understand the current frontend, backend, testing, and deployment setup. Then plan the Dockerfiles, docker-compose.yml, and GitHub Action around the stated development, deployment, architecture, and runtime-variable requirements. Done means cross-platform development support, x86 and arm64 images uploaded to ghcr.io, deployment guidance, and updated documentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, github-actions, google-cloud, python
Domain
build-system, ci-cd, cloud, devops, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.