Skip to content
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

Detachable Server Execution #3315

Conversation

JaiPannu-IITI
Copy link

@JaiPannu-IITI JaiPannu-IITI commented Feb 27, 2025

Overview

Depricating pnpm run start_development_server from postCreateCommand to gain complete control how server is start.
This allows us to start server inside docker and detach cli from it safely.

Recommended cron job:

cd /home/talawa-api/talawa-api && docker compose down --rmi all --volumes && docker compose down --rmi all --volumes && git checkout --force develop-postgres && git fetch upstream && git reset upstream/develop-postgres --hard && rm -rf node_modules && pnpm install && cp -f envFiles/.env.devcontainer .env && sed -i "s|MAPPED_PORT=80|MAPPED_PORT=8080|g" .env && sed -i "s|MAPPED_PORT=443|MAPPED_PORT=8443|g" .env && devcontainer build --workspace-folder . && devcontainer up --workspace-folder . && docker exec talawa-api-1 /bin/bash -c 'nohup pnpm run start_development_server > /dev/null 2>&1 &'

For sample data it remains same

Note: This ensures successful execution provided cron has access to crud operation and deamon/pnpm, also docker service is running

Screenshots

image

This was run with above command , we can notice that in the end it does not struck to server listening but that in run inside docker in the back and detached safely

image

Summary by CodeRabbit

  • Chores

    • Updated the environment setup process by removing the automatic start of the development server, streamlining post-setup tasks.
  • Documentation

    • Enhanced the developer guides with clearer instructions for resetting the Docker environment.
    • Provided revised directions detailing two distinct modes for launching the development container and a more informative installation output format.

@JaiPannu-IITI JaiPannu-IITI marked this pull request as ready for review February 27, 2025 23:24
Copy link

coderabbitai bot commented Feb 27, 2025

Walkthrough

The changes adjust the post-creation behavior of the development container and update related documentation. In the development container configuration, the command that automatically starts the development server has been removed so that only setup tasks (ownership changes, dependency installation, and corepack enabling) remain. Meanwhile, documentation updates now include a new command to manually start the development server inside the Docker container and revised instructions for starting the container in “Attached Mode” or “Detached Mode” with a structured JSON output.

Changes

File(s) Change Summaries
.devcontainer/devcontainer.json Modified postCreateCommand to remove the automatic execution of the development server while retaining ownership adjustments, dependency installation, and corepack enabling.
docs/docs/.../testing.md
docs/docs/.../installation.md
Updated developer instructions: added a Docker command in testing documentation to start the dev server and restructured installation steps with distinct attached/detached modes and JSON output details.

Possibly related PRs

  • fix corepack & pnpm compatibility #3161: The changes in the main PR, which remove the command to start the development server from the postCreateCommand in .devcontainer/devcontainer.json, are related to the modifications in the retrieved PR that also involve changes to the postCreateCommand in the same file, specifically regarding package manager setup and initialization commands.
  • Fixed installation documentation #3101: The changes in the main PR, which remove the command to start the development server from the .devcontainer/devcontainer.json, are related to the retrieved PR that enhances the instructions for starting the development server in the installation documentation, as both involve modifications to the server startup process.
  • Docker compose import #3191: The changes in the main PR, which remove the command to start the development server from the .devcontainer/devcontainer.json, are related to the retrieved PR that adds a command to start the development server in the Docker environment, indicating a direct connection in the context of server startup commands.

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

  • palisadoes

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8ac8790 and c4a67a3.

📒 Files selected for processing (1)
  • docs/docs/docs/getting-started/installation.md (2 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/docs/docs/getting-started/installation.md

[grammar] ~310-~310: The word “output” is spelled as one word.
Context: ...tallation is complete, the last line of out put should look like this: ``` ... ... {"o...

(OUT_COMPOUNDS)

🪛 markdownlint-cli2 (0.17.2)
docs/docs/docs/getting-started/installation.md

310-310: Ordered list item prefix
Expected: 1; Actual: 12; Style: 1/1/1

(MD029, ol-prefix)


312-312: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


334-334: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


340-340: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

⏰ Context from checks skipped due to timeout of 90000ms (1)

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

codecov bot commented Feb 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 48.57%. Comparing base (d38e6a8) to head (d5b2aee).

Additional details and impacted files
@@                Coverage Diff                @@
##           develop-postgres    #3315   +/-   ##
=================================================
  Coverage             48.57%   48.57%           
=================================================
  Files                   458      458           
  Lines                 34489    34489           
  Branches                971      971           
=================================================
  Hits                  16752    16752           
  Misses                17737    17737           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 5

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d38e6a8 and 8ac8790.

📒 Files selected for processing (3)
  • .devcontainer/devcontainer.json (1 hunks)
  • docs/docs/docs/developer-resources/testing.md (1 hunks)
  • docs/docs/docs/getting-started/installation.md (2 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/docs/docs/getting-started/installation.md

[grammar] ~310-~310: The word “output” is spelled as one word.
Context: ...tallation is complete, the last line of out put should look like this: ``` ... ... ......

(OUT_COMPOUNDS)

🪛 markdownlint-cli2 (0.17.2)
docs/docs/docs/getting-started/installation.md

310-310: Ordered list item prefix
Expected: 1; Actual: 12; Style: 1/1/1

(MD029, ol-prefix)


312-312: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


335-335: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


341-341: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

⏰ Context from checks skipped due to timeout of 90000ms (2)
🔇 Additional comments (1)
.devcontainer/devcontainer.json (1)

70-74: Deprecate Automatic Server Startup in postCreateCommand
The removal of the pnpm run start_development_server command from the postCreateCommand aligns perfectly with the PR objective. This change now delegates the responsibility of starting the server to a manual invocation. Please ensure that the remaining initialization steps (ownership changes, dependency installation, and enabling corepack) fully cover the necessary setup tasks.

@Cioppolo14 Cioppolo14 closed this Feb 28, 2025
@Cioppolo14
Copy link
Contributor

There isn’t an issue assigned to you for this PR. Please follow the guidelines in our PR_GUIDELINES.md file. We have the procedures in place so that everyone has a fair chance of contributing. I will be closing this pull request. Please follow the procedures and resubmit when ready.

@JaiPannu-IITI
Copy link
Author

JaiPannu-IITI commented Feb 28, 2025

@Cioppolo14 I am sorry, I forgot to mention issue, Raising another PR with proper reference.

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