Skip to content

Add "Development" Homepage category, move/stop services - #186

Merged
bubacoder merged 2 commits into
mainfrom
feature/categories
Aug 23, 2025
Merged

Add "Development" Homepage category, move/stop services#186
bubacoder merged 2 commits into
mainfrom
feature/categories

Conversation

@bubacoder

@bubacoder bubacoder commented Aug 23, 2025

Copy link
Copy Markdown
Owner

Summary by CodeRabbit

  • New Features

    • Added a “Development” section to the dashboard with a 4‑column row layout for clearer organization.
  • Changes

    • Moved Code Server, GitLab, and Jupyter Notebook tiles from “Tools” to the new “Development” section.
  • Chores

    • Updated service defaults: Radarr, Sonarr, Bazarr, Prowlarr, Jellyseerr, FlareSolverr, and Tales are now set to remain off by default.
    • Enabled Readarr configuration (previously commented) but set it to remain off by default.
    • Removed WatchYourLAN from the security group.

@coderabbitai

coderabbitai Bot commented Aug 23, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Introduces a new "Development" group in the dashboard layout and moves dev services (code-server, GitLab, Jupyter) into that group via Traefik homepage labels. Updates host services configuration to set several services to down, adds/uncomments Readarr (down), and removes watchyourlan from security.

Changes

Cohort / File(s) Summary
Host services state updates
config-example/docker/myhost/services.yaml
Set multiple services to down (radarr, sonarr, bazarr, prowlarr, jellyseerr, flaresolverr, tales). Uncommented/added readarr with state down. Removed watchyourlan from security group.
Dashboard layout: Development group
docker/dashboard/homepage/config/settings.yaml
Added layout.Development block with style: row and columns: 4, positioned between Tools and Connections.
Relabel dev services to Development
docker/dev/code-server.yaml, docker/dev/gitlab.yaml, docker/dev/jupyter-notebook.yaml
Changed Traefik label homepage.group from "Tools" to "Development" for code-server, GitLab, and Jupyter Notebook.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/categories

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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

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

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.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
config-example/docker/myhost/services.yaml (1)

147-163: Multiple Arr services set to down; consider adding rationale notes for maintainability.

Future you (or others) may wonder why these were disabled. Adding short notes improves clarity in ops runbooks and avoids accidental re-enables.

Example diff adding brief notes (tweak as needed):

   - arr:
     - name: radarr
-      state: down
+      state: down
+      note: temporarily disabled
     - name: sonarr
-      state: down
+      state: down
+      note: temporarily disabled
     - name: bazarr
-      state: down
+      state: down
+      note: temporarily disabled
     # TODO replace with Lazy Librarian
     - name: readarr
-      state: down
+      state: down
+      note: planned replacement pending
     - name: prowlarr
-      state: down
+      state: down
+      note: temporarily disabled
     - name: jellyseerr
-      state: down
+      state: down
+      note: temporarily disabled
     - name: flaresolverr
-      state: down
+      state: down
+      note: temporarily disabled
 ...
   - personal:
     - name: tales
-      state: down
+      state: down
+      note: temporarily disabled

Also applies to: 172-172

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 5006458 and 727e752.

📒 Files selected for processing (5)
  • config-example/docker/myhost/services.yaml (2 hunks)
  • docker/dashboard/homepage/config/settings.yaml (1 hunks)
  • docker/dev/code-server.yaml (1 hunks)
  • docker/dev/gitlab.yaml (1 hunks)
  • docker/dev/jupyter-notebook.yaml (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{sh,Dockerfile,yml,yaml,tf}

📄 CodeRabbit inference engine (CLAUDE.md)

Follow the pre-commit rules defined in .pre-commit-config.yaml, which includes linting for shell scripts, Dockerfiles, YAML files, Ansible playbooks, and Terraform configurations.

Files:

  • docker/dev/gitlab.yaml
  • docker/dev/code-server.yaml
  • docker/dev/jupyter-notebook.yaml
  • config-example/docker/myhost/services.yaml
  • docker/dashboard/homepage/config/settings.yaml
docker/**/*.{yml,yaml}

📄 CodeRabbit inference engine (CLAUDE.md)

Docker Compose files for services should be placed under the docker/ directory, organized by service type (e.g., security, media, storage, monitoring).

Files:

  • docker/dev/gitlab.yaml
  • docker/dev/code-server.yaml
  • docker/dev/jupyter-notebook.yaml
  • docker/dashboard/homepage/config/settings.yaml
config-example/**

📄 CodeRabbit inference engine (CLAUDE.md)

Example configuration files should be placed under the config-example/ directory.

Files:

  • config-example/docker/myhost/services.yaml
🔇 Additional comments (4)
docker/dev/code-server.yaml (1)

39-39: Move to Development group is correct and consistent with the new layout.

This aligns code-server with the newly added "Development" section in the homepage settings. No functional impact; LGTM.

docker/dev/gitlab.yaml (1)

44-44: GitLab now grouped under Development — looks good.

Label change is consistent with other dev services and the new homepage layout.

docker/dev/jupyter-notebook.yaml (1)

25-25: Jupyter Notebook moved to Development — approved.

Matches the new layout and keeps dev tooling together.

docker/dashboard/homepage/config/settings.yaml (1)

27-29: Verified Development layout configuration

All sanity checks have passed, confirming cross-file consistency for the new Development section:

  • docker/dev/*.yaml service files (code-server, GitLab, Jupyter Notebook) are all labeled with homepage.group: Development.
  • docker/dashboard/homepage/config/settings.yaml includes a layout.Development block with columns: 4.
  • config-example/docker/myhost/services.yaml’s dev group lists code-server, gitlab, and jupyter-notebook (with expected states).

Approve code changes.

@bubacoder
bubacoder merged commit b58b51a into main Aug 23, 2025
4 checks passed
@bubacoder
bubacoder deleted the feature/categories branch August 23, 2025 18:39
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.

1 participant