Skip to content

docs: fix dead systemd setup link - #1840

Open
sarankumar1325 wants to merge 1 commit into
parseablehq:mainfrom
sarankumar1325:docs/fix-systemd-docs-link
Open

sarankumar1325 wants to merge 1 commit into
parseablehq:mainfrom
sarankumar1325:docs/fix-systemd-docs-link

Conversation

@sarankumar1325

@sarankumar1325 sarankumar1325 commented Oct 30, 2026 •

Copy link
Copy Markdown

Description

The link in systemd/README.md (https://www.parseable.io/docs/installation/systemd) returns 404. The systemd setup guides now live on the Linux pages under self-hosted installation:

This PR points the README at both pages and notes which service file in this folder each one uses. Both URLs return 200 (checked with curl). Docs-only, no code change.

AI assistance: I prepared this change with an AI coding assistant and reviewed it myself.


This PR has:

  • been tested to ensure log ingestion and log query works. (n/a, docs only)
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader. (n/a)
  • added documentation for new or modified features or behaviors.

Summary by CodeRabbit

  • Documentation
    • Added separate setup links for standalone deployments using local storage or S3, and for distributed S3 clusters.
    • Clarified which service files are used for each deployment type.

parseable.io/docs/installation/systemd returns 404. The systemd guides
now live under parseable.com/docs/self-hosted/installation/ (standalone
and distributed Linux pages).

Signed-off-by: sarankumar1325 <120080287+sarankumar1325@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request

@coderabbitai

coderabbitai Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Repository UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 4637b175-26df-447d-95d9-5e8339caf161
Commits

Reviewing files that changed from the base of the PR and between 60ce88c and b9d932e.

Files selected for processing: 1
  • systemd/README.md

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

Walkthrough

The systemd README replaces one setup link with separate links for standalone deployments and distributed S3 clusters. It names the service files used for each deployment type.

Changes

Systemd setup documentation

Layer / File(s) Summary
Deployment setup links
systemd/README.md
The README links to standalone and distributed S3 setup instructions. It names parseable.local.service or parseable.s3.service for standalone deployments and parseable.s3.service for distributed clusters.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Suggested reviewers: nitisht

Merge Risk: Minimal · up to b9d93

The documentation-only update introduces no established runtime or deployment risk.

Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly and concisely identifies the documentation change: fixing the broken systemd setup link.
Description check Passed The description explains the broken link, identifies the replacement standalone and distributed guides, records URL checks, states the scope is documentation-only, and completes the relevant checklist…
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

The description explains the broken link, identifies the replacement standalone and distributed guides, records URL checks, states the scope is documentation-only, and completes the relevant checklist item. The issue reference is not required because no issue is identified.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Finishing Touches: 💡 1
🛠️ Fix failing CI checks: 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

A rabbit reads the setup page,
Two paths now share the systemd stage.
Local or S3, the links are clear,
Cluster steps are listed here.
A service name for each way,
Then off the rabbit hops away.

Comment @coderabbitai help to get the list of available commands.

@nitisht

nitisht commented Oct 31, 2026

Copy link
Copy Markdown
Member

Thanks for the fix @sarankumar1325 - can you add the comment (to sign the CLA),

This branch has not been deployed

No deployments
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