-
Notifications
You must be signed in to change notification settings - Fork 0
feat: handle dockerize core app #272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Caution Review failedThe pull request is closed. WalkthroughA new multi-stage Dockerfile was introduced in the core application to optimize the build process and enhance security. The Next.js configuration now specifies a standalone output, and the docker-compose file was updated with changes to service naming, container properties, Dockerfile path, and restart policy. Additionally, new scripts and dependency updates were added across various package.json files—including CI preparation functionality and improvements to build scripts—while code formatting adjustments were made in design system scripts. Changes
Sequence Diagram(s)sequenceDiagram
participant Dev as Developer
participant Docker as Docker Engine
participant Base as Base Stage
participant Builder as Builder Stage
participant Installer as Installer Stage
participant Runner as Runner Stage
Dev->>Docker: Trigger Docker build
Docker->>Base: Execute base stage (Node.js 18-alpine)
Docker->>Builder: Set up workdir, install dependencies, run Turbo CLI, copy files, and prune build
Docker->>Installer: Install packages and build project from builder output
Docker->>Runner: Copy built files, set non-root user, and configure for production
Docker->>Dev: Final Docker image ready
sequenceDiagram
participant User as User
participant Prep as prepare.js
participant Pkg as package.json
User->>Prep: Execute prepare.js
Prep->>Pkg: Read package.json content
Prep->>Prep: Update packageManager field to [email protected]
Prep->>Pkg: Write updated package.json back to disk
Prep->>User: Log success message
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (9)
✨ Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
feat: handle dockerize core app
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
Closes #263
Summary by CodeRabbit
New Features
Improvements