Bootstrap repository readiness artifacts by codepress-dev[bot] · Pull Request #61 · quantfive/django-react-intro · GitHub
Skip to content

Bootstrap repository readiness artifacts - #61

Open
codepress-dev[bot] wants to merge 1 commit into
masterfrom
codepress/dev@codepress.dev/you-are-orchestrating-repository-7844f333
Open

codepress-dev[bot] wants to merge 1 commit into
masterfrom
codepress/dev@codepress.dev/you-are-orchestrating-repository-7844f333

Conversation

@codepress-dev

@codepress-dev codepress-dev Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

This prepares the repository for dependable CodePress development workflows: pull requests can carry useful frontend screenshots, the React app can be started in a repeatable container, and future sessions have a local verification contract to check the public Home experience.

Technical details

Added generated repository skills for PR screenshots, app-server startup, and local verification. The screenshot workflow maps the single public React route (/) and validates a real Chromium render. The app-server path adds a self-contained Node 18/Yarn 1 image for the legacy Create React App frontend, a root ignore file, and a schema-versioned recipe on port 3000; it deliberately preserves the existing Live Dev Server artifacts and does not pretend the separate legacy Django service has a canonical combined start command. The verify-local skill documents that scope and covers the live HTML shell, JavaScript bundle, public manifest, browser render, and log review.

The main compatibility choice is to run the 2017 CRA toolchain with Node 18 and Yarn 1.22.22, with dependencies installed during image build and the server bound to 0.0.0.0. The remaining reviewer concern is the separate Django 1.11/Pipenv service, which still needs its own runtime/bootstrap decision before it can be included in a full-stack verification path.

Generated with CodePress

Changes

  • Add the generated PR screenshot skill for the public React Home route.
  • Add Dockerfiles and .dockerignore for repeatable CRA app-server startup.
  • Add the app-server recipe and generated start-app-server skill.
  • Add the generated verify-local contract for the frontend surface.

Test plan

  • Run the recipe-backed app server and verify GET / returns HTTP 200 with the CRA HTML shell.
  • Verify GET /static/js/bundle.js and GET /manifest.json return HTTP 200 with the expected content types.
  • Run the local verification skill and confirm Chromium renders the React logo, the Welcome to React heading, and starter content without flow-related log errors.

Open items

  • The generated recipe intentionally targets only the React frontend. The separate Django 1.11 backend remains outside the local contract until a canonical combined start path and compatible runtime are defined.

Authors

Generated with CodePress · View the chat session

Co-authored-by: dev@codepress.dev dev@codepress.dev

Co-authored-by: dev@codepress.dev <dev@codepress.dev>
@codepress-dev codepress-dev Bot added the cp:in-progress CodePress: still being worked on label Aug 6, 2026
@codepress-dev

codepress-dev Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

@lightninglu10 lightninglu10 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QA verification review: please confirm the generated repository-readiness setup PR in the originating CodePress bootstrap session.

@lightninglu10 lightninglu10 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QA verification review: the generated repository-readiness setup PR is ready for the repository-specific workflow review in the originating CodePress bootstrap session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cp:in-progress CodePress: still being worked on

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant