chore: move the rts.conf code to shell file#38859
Conversation
WalkthroughA new shell script Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
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
Documentation and Community
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
deploy/docker/fs/opt/appsmith/templates/supervisord/application_process/rts.conf (1)
2-2: Consider adding error handling to the shell script.Since this is a critical service startup script, consider adding basic error handling in
run-rts.sh.Add these checks to the shell script:
#!/bin/bash + +if [ ! -f "/opt/appsmith/rts/bundle/server.js" ]; then + echo "Error: RTS server.js not found" + exit 1 +fi + exec node /opt/appsmith/rts/bundle/server.js
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
deploy/docker/fs/opt/appsmith/run-rts.sh(1 hunks)deploy/docker/fs/opt/appsmith/templates/supervisord/application_process/rts.conf(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- deploy/docker/fs/opt/appsmith/run-rts.sh
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: perform-test / rts-build / build
- GitHub Check: perform-test / client-build / client-build
- GitHub Check: perform-test / server-build / server-unit-tests
🔇 Additional comments (1)
deploy/docker/fs/opt/appsmith/templates/supervisord/application_process/rts.conf (1)
2-2: Verify shell script setup and permissions.The change to use a wrapper script improves extensibility. However, ensure the following:
- The shell script exists at
/opt/appsmith/run-rts.sh- The script has proper executable permissions
|
/build-deploy-preview skip-tests=true |
|
Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/13004493587. |
|
Deploy-Preview-URL: https://ce-38859.dp.appsmith.com |
Description
Tip
Moving the
rts.confrunning code to shell file for more extensibility.Fixes #
Issue Numberor
Fixes
Issue URLWarning
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.
Automation
/ok-to-test tags="@tag.Sanity"
🔍 Cypress test results
Tip
🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/13004107300
Commit: b8af6b5
Cypress dashboard.
Tags:
@tag.SanitySpec:
Tue, 28 Jan 2025 05:59:53 UTC
Communication
Should the DevRel and Marketing teams inform users about this change?
Summary by CodeRabbit
run-rts.sh) to manage the execution of the Node.js application