Skip to content

Migrate to backend-only architecture and remove Next.js - #21

Open
pinkycollie wants to merge 4 commits into
mainfrom
backend-only-agnostic-platform-4601368575468098205
Open

Migrate to backend-only architecture and remove Next.js#21
pinkycollie wants to merge 4 commits into
mainfrom
backend-only-agnostic-platform-4601368575468098205

Conversation

@pinkycollie

Copy link
Copy Markdown
Owner

This refactor removes Next.js and all frontend-related files, replacing them with a standalone Express/TypeScript server. It introduces a secure, frontend-agnostic API for AI chat, video processing, and PinkSync estimation, using bcryptjs for password hashing and JWT for authentication. Deployment configurations for Docker and Docker Compose have been updated accordingly.


PR created automatically by Jules for task 4601368575468098205 started by @pinkycollie

- Removed Next.js, React, and all frontend-related files and dependencies.
- Implemented a standalone Express/TypeScript server in the 'server/' directory.
- Developed a frontend-agnostic API layer for AI chat, video processing, and PinkSync estimation.
- Replaced insecure mock authentication with robust bcryptjs hashing and JWT-based authorization.
- Added security middleware including Helmet, CORS, and rate limiting.
- Updated Docker and Docker Compose configurations for the new backend-only service.
- Documented the new agnostic API and integration paths for Unity/visual systems.
- Verified system build and established basic test infrastructure.

Co-authored-by: pinkycollie <199848471+pinkycollie@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

google-labs-jules Bot and others added 3 commits March 28, 2026 16:16
- Transitioned the platform to a backend-only, frontend-agnostic architecture.
- Preserved 'components/' and 'templates/' directories as a generative source library for AI-driven development.
- Implemented a standalone Express/TypeScript server in the 'server/' directory.
- Introduced a new code generation endpoint at '/api/generate/code' for creating accessible React/Vite/Deaf-inclusive UIs.
- Replaced insecure mock authentication with robust bcryptjs hashing and JWT-based authorization.
- Added security middleware including Helmet, CORS, and rate limiting.
- Integrated the PinkSync Estimator within the backend as an accessible service.
- Updated Docker and Docker Compose configurations for the new backend-only agnostic deployment.
- Documented the new agnostic API and the vision for the generative platform.
- Verified system build and established basic test infrastructure.

Co-authored-by: pinkycollie <199848471+pinkycollie@users.noreply.github.com>
- Removed Next.js runtime and frontend-specific configuration.
- Preserved 'components/' and 'templates/' as a generative source library.
- Implemented a secure standalone Express backend (Agnostic Layer).
- Developed core services: DeafAUTH, PinkSync, Fibonrose, and PinkFlow (A11y Node).
- Established AI services (video-pipeline and language-model) as the unified entry point.
- Updated Docker and Docker Compose for the new backend-only architecture.
- Provided comprehensive agnostic API documentation in 'docs/API_AGNOSTIC.md'.
- Verified system build and established basic test infrastructure.

Co-authored-by: pinkycollie <199848471+pinkycollie@users.noreply.github.com>
- Consolidated all backend logic into a single 'server/index.ts' (Express/Node).
- Implemented service wrappers for DeafAUTH, PinkSync, Fibonrose, and PinkFlow.
- Masked internal service URLs for enhanced security (e.g., '/_/a', '/_/g').
- Added a Zero Trust Auth Tunnel middleware for all protected service access.
- Simplified Docker and Docker Compose for minimal node deployment.
- Maintained 'components/' and 'templates/' as the generative source library.
- Updated documentation for the minimal, masked agnostic API.
- Verified build and basic test infrastructure.

Co-authored-by: pinkycollie <199848471+pinkycollie@users.noreply.github.com>

@pinkycollie pinkycollie left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

@Claude

Claude AI commented Apr 28, 2026

Copy link
Copy Markdown

@pinkycollie Unfortunately I hit an unexpected error while processing your comment. I've automatically reported this to GitHub.

You can ask me to try again later by mentioning me in a new comment.

If you want to contact GitHub about this error, please mention the following identifier so they can better serve you: 58b3b3b1-8c1e-4de9-a574-e75ab96cc761

Sorry for the inconvenience!

5 similar comments
@Claude

Claude AI commented Apr 28, 2026

Copy link
Copy Markdown

@pinkycollie Unfortunately I hit an unexpected error while processing your comment. I've automatically reported this to GitHub.

You can ask me to try again later by mentioning me in a new comment.

If you want to contact GitHub about this error, please mention the following identifier so they can better serve you: 58b3b3b1-8c1e-4de9-a574-e75ab96cc761

Sorry for the inconvenience!

@Claude

Claude AI commented Apr 28, 2026

Copy link
Copy Markdown

@pinkycollie Unfortunately I hit an unexpected error while processing your comment. I've automatically reported this to GitHub.

You can ask me to try again later by mentioning me in a new comment.

If you want to contact GitHub about this error, please mention the following identifier so they can better serve you: 58b3b3b1-8c1e-4de9-a574-e75ab96cc761

Sorry for the inconvenience!

@Claude

Claude AI commented Apr 28, 2026

Copy link
Copy Markdown

@pinkycollie Unfortunately I hit an unexpected error while processing your comment. I've automatically reported this to GitHub.

You can ask me to try again later by mentioning me in a new comment.

If you want to contact GitHub about this error, please mention the following identifier so they can better serve you: 58b3b3b1-8c1e-4de9-a574-e75ab96cc761

Sorry for the inconvenience!

@Claude

Claude AI commented Apr 28, 2026

Copy link
Copy Markdown

@pinkycollie Unfortunately I hit an unexpected error while processing your comment. I've automatically reported this to GitHub.

You can ask me to try again later by mentioning me in a new comment.

If you want to contact GitHub about this error, please mention the following identifier so they can better serve you: 58b3b3b1-8c1e-4de9-a574-e75ab96cc761

Sorry for the inconvenience!

@Claude

Claude AI commented Apr 28, 2026

Copy link
Copy Markdown

@pinkycollie Unfortunately I hit an unexpected error while processing your comment. I've automatically reported this to GitHub.

You can ask me to try again later by mentioning me in a new comment.

If you want to contact GitHub about this error, please mention the following identifier so they can better serve you: 58b3b3b1-8c1e-4de9-a574-e75ab96cc761

Sorry for the inconvenience!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants