Skip to content

docs: install from source#8369

Merged
mendonk merged 24 commits into
mainfrom
docs-install-from-source
Jun 30, 2025
Merged

docs: install from source#8369
mendonk merged 24 commits into
mainfrom
docs-install-from-source

Conversation

@mendonk
Copy link
Copy Markdown
Collaborator

@mendonk mendonk commented Jun 4, 2025

  • Improve instructions on cloning/forking and building from source.
  • Link to contributing from Install page.
  • Add more information on the make run_cli command.
  • Add to CONTRIBUTING.md also.

Summary by CodeRabbit

  • Documentation
    • Updated installation instructions with a detailed "Install Langflow from source" section featuring step-by-step setup using Make.
    • Expanded the contribution guide into a comprehensive manual covering setup, development, testing, debugging, and pull request best practices.
    • Added references to the source installation guide in the getting started documentation for easier access.
    • Improved formatting and consistency in README and contributing documents for better clarity and navigation.

@mendonk mendonk self-assigned this Jun 4, 2025
@dosubot dosubot Bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Jun 4, 2025
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 4, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The changes update documentation to provide clearer and more detailed instructions for installing and running Langflow from source. This includes enhancements to the README, contribution guide, and installation documentation, with step-by-step setup using Make, expanded configuration options, and cross-references between relevant documentation sections.

Changes

File(s) Change Summary
README.md Removed trailing space in a list item.
docs/docs/Contributing/contributing-how-to-contribute.md, CONTRIBUTING.md Retitled and extensively expanded contribution instructions into a detailed "Install Langflow from source" guide with Make-based setup, testing, debugging, and PR guidelines.
docs/docs/Get-Started/get-started-installation.md Added a subsection linking to the new "Install Langflow from source" documentation.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Documentation
    participant Repository
    participant Make

    User->>Documentation: Reads "Install from source" instructions
    User->>Repository: Clones Langflow repository
    User->>Make: Runs `make init`
    Make->>Make: Installs dependencies, cleans cache, builds frontend, starts app
    User->>Make: (Optional) Runs `make run_cli` with custom options
    Make->>Make: Starts Langflow with user-defined settings
Loading

Possibly related PRs

Suggested labels

size:S, lgtm

Suggested reviewers

  • edwinjosechittilappilly
✨ Finishing Touches
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch docs-install-from-source

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests 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.

@mendonk mendonk requested a review from KimberlyFields June 4, 2025 15:34
@dosubot dosubot Bot added the documentation Improvements or additions to documentation label Jun 4, 2025
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jun 4, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2025

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jun 4, 2025
Copy link
Copy Markdown
Contributor

@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: 1

🔭 Outside diff range comments (1)
docs/docs/Contributing/contributing-how-to-contribute.md (1)

21-29: ⚠️ Potential issue

Missing initial clone instruction.
The guide asks to fork and add a fork remote but never tells the user to clone the repository. Please insert a step to clone your fork or the upstream repo before adding remotes.

🧹 Nitpick comments (2)
docs/docs/Contributing/contributing-how-to-contribute.md (2)

17-20: Consider adding Python prerequisite.
The Make-based setup assumes Python is already installed (for uv). Adding * Python 3.10–3.13 to prerequisites will prevent confusion.


43-50: Unify list style for bullet points.
Markdown lint prefers asterisks (*) over hyphens (-). For consistency, replace hyphens in the feature list with asterisks.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

44-44: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


45-45: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


46-46: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


47-47: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


48-48: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5abb545 and 5b03f46.

📒 Files selected for processing (3)
  • README.md (2 hunks)
  • docs/docs/Contributing/contributing-how-to-contribute.md (2 hunks)
  • docs/docs/Get-Started/get-started-installation.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/docs/Contributing/contributing-how-to-contribute.md

[uncategorized] ~61-~61: A punctuation mark might be missing here.
Context: ... | |-----------|---------|-------------| | log_level | debug | Set the loggin...

(AI_EN_LECTOR_MISSING_PUNCTUATION)

🪛 markdownlint-cli2 (0.17.2)
docs/docs/Contributing/contributing-how-to-contribute.md

44-44: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


45-45: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


46-46: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


47-47: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


48-48: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)

🔇 Additional comments (8)
docs/docs/Get-Started/get-started-installation.md (1)

68-71: Link to source installation is well placed and correct.
The new subsection cleanly references the detailed guide and uses the proper anchor.

README.md (1)

20-20: Trailing whitespace removal in feature list is correct.
The formatting inconsistency has been fixed.

docs/docs/Contributing/contributing-how-to-contribute.md (6)

11-14: Section introduction looks good.
The new "Install Langflow from source" section is appropriately placed and clearly titled.


31-41: Environment setup steps are clear.
Changing into the repo root and running make init is well documented.


51-57: make run_cli instructions are clear.
The example command and parameter explanation are accurate and helpful.


59-67: Parameter table formatting is good.
The table clearly documents make run_cli options.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~61-~61: A punctuation mark might be missing here.
Context: ... | |-----------|---------|-------------| | log_level | debug | Set the loggin...

(AI_EN_LECTOR_MISSING_PUNCTUATION)


69-74: Pre-commit hook instructions are correct.
The optional hook setup is well explained, including the note on using uv run git commit.


78-79:

Details

✅ Verification successful

Verify Makefile targets.
Ensure that the Makefile defines unit_tests and tests targets as referenced here. You can run:

to confirm.


🏁 Script executed:

grep -E "unit_tests:|tests:" Makefile

Length of output: 136


Makefile targets confirmed
The Makefile defines both unit_tests and tests targets as referenced in the docs, so no changes are needed.

  • unit_tests: ## run unit tests
  • tests: ## run unit, integration, coverage tests

Comment thread README.md Outdated
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2025

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

Copy link
Copy Markdown
Collaborator

@edwinjosechittilappilly edwinjosechittilappilly left a comment

Choose a reason for hiding this comment

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

🚀 Getting Started with Langflow

1. Prerequisites

  • uv (Python package/dependency manager)
  • npm (Node.js package manager)

2. Install All Dependencies

This will install both backend and frontend dependencies, build the frontend, and get everything ready:

make init

3. Run the Application

To start the backend and serve the frontend:

make run_cli

4. Common Development Commands

  • Install only frontend dependencies:
    make install_frontend
  • Build frontend static files:
    make build_frontend
  • Install only backend dependencies:
    make install_backend
  • Run frontend in development mode (hot reload):
    make frontend
  • Run backend in development mode:
    make backend

5. Code Quality & Testing

  • Format code (backend & frontend):
    make format
  • Run all tests:
    make tests
  • Run only unit tests:
    make unit_tests
  • Run only integration tests:
    make integration_tests

6. Clean Up

  • Clean Python cache:
    make clean_python_cache
  • Clean npm cache and frontend build:
    make clean_npm_cache
  • Clean everything:
    make clean_all

For more commands, run:

make help

This will list all available Makefile targets and their descriptions.

@edwinjosechittilappilly
Copy link
Copy Markdown
Collaborator

@mendonk can you take a look at adding Points 4 and 5 from the above content in the docs?

@dosubot dosubot Bot added size:L This PR changes 100-499 lines, ignoring generated files. and removed size:M This PR changes 30-99 lines, ignoring generated files. labels Jun 9, 2025
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jun 9, 2025
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jun 26, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 26, 2025

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

Comment thread CONTRIBUTING.md Outdated
@dosubot dosubot Bot added the lgtm This PR has been approved by a maintainer label Jun 26, 2025
Comment thread CONTRIBUTING.md Outdated
Copy link
Copy Markdown
Collaborator

@aimurphy aimurphy left a comment

Choose a reason for hiding this comment

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

Some comments to possibly help with clarity, but nothing critical.

Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md
Comment thread CONTRIBUTING.md Outdated
Co-authored-by: April I. Murphy <36110273+aimurphy@users.noreply.github.com>
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jun 30, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 30, 2025

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jun 30, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 30, 2025

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jun 30, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 30, 2025

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft

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

Labels

documentation Improvements or additions to documentation lgtm This PR has been approved by a maintainer size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants