[PR #783] ref(booklore): remove booklore since it was closed #9330

New Issue

GiteaMirror · 2026-06-02T06:09:51-05:00

GiteaMirror commented

2026-06-02 06:09:51 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/783
Author: @irg1008
Created: 4/9/2026
Status: 🔄 Open

Base: canary ← Head: canary

📝 Commits (1)

8af55b2 ref(booklore): remove booklore since it was closed

📊 Changes

4 files changed (+0 additions, -81 deletions)

View changed files

➖ blueprints/booklore/docker-compose.yml (+0 -39)
➖ blueprints/booklore/image.png (+0 -0)
➖ blueprints/booklore/template.toml (+0 -24)
📝 meta.json (+0 -18)

📄 Description

Repo was closed by owner after accusations of obscure telemetry practices and overuse of AI. A fork was created called Grimmory

What is this PR about?

Removes booklore after the repo was closed

Checklist

Before submitting this PR, please make sure that:

I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
[ x I have added tests that demonstrate that my correction works or that my new feature works.

Close automatically the related issues using the keywords: closes #ISSUE_NUMBER

Screenshots or Videos

Greptile Summary

This PR removes the booklore template from the repository following the closure of the upstream project (booklore-app/BookLore) by its owner. All three blueprint files (docker-compose.yml, image.png, template.toml) are deleted and the corresponding entry is cleanly removed from meta.json.

Confidence Score: 5/5

Safe to merge — all deletions are complete and consistent with no residual references.

The PR is a pure deletion with no logic changes. All blueprint files and the meta.json entry are removed in full, and the sort order in meta.json is preserved. No P1 or P0 findings.

No files require special attention.

Vulnerabilities

No security concerns identified.

_{Reviews (1): Last reviewed commit: "ref(booklore): remove booklore since it ..." | Re-trigger Greptile}

_{(2/5) Greptile learns from your feedback when you react with thumbs up/down!}

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Dokploy/templates/pull/783 **Author:** [@irg1008](https://github.com/irg1008) **Created:** 4/9/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `canary` --- ### 📝 Commits (1) - [`8af55b2`](https://github.com/Dokploy/templates/commit/8af55b21f494f66bec6ac37a377c5a1d66a77127) ref(booklore): remove booklore since it was closed ### 📊 Changes **4 files changed** (+0 additions, -81 deletions) <details> <summary>View changed files</summary> ➖ `blueprints/booklore/docker-compose.yml` (+0 -39) ➖ `blueprints/booklore/image.png` (+0 -0) ➖ `blueprints/booklore/template.toml` (+0 -24) 📝 `meta.json` (+0 -18) </details> ### 📄 Description Repo was closed by owner after accusations of obscure telemetry practices and overuse of AI. A fork was created called [Grimmory](https://github.com/grimmory-tools/grimmory) ## What is this PR about? Removes booklore after [the repo was closed](https://www.reddit.com/r/selfhosted/comments/1rvmpnv/booklore_is_gone/) ## Checklist Before submitting this PR, please make sure that: - [x] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template - [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong. - [ x I have added tests that demonstrate that my correction works or that my new feature works. ## Issues related (if applicable) Close automatically the related issues using the keywords: `closes #ISSUE_NUMBER` ## Screenshots or Videos  <h3>Greptile Summary</h3> This PR removes the booklore template from the repository following the closure of the upstream project (`booklore-app/BookLore`) by its owner. All three blueprint files (`docker-compose.yml`, `image.png`, `template.toml`) are deleted and the corresponding entry is cleanly removed from `meta.json`. <h3>Confidence Score: 5/5</h3> Safe to merge — all deletions are complete and consistent with no residual references. The PR is a pure deletion with no logic changes. All blueprint files and the meta.json entry are removed in full, and the sort order in meta.json is preserved. No P1 or P0 findings. No files require special attention. <details open><summary><h3>Vulnerabilities</h3></summary> No security concerns identified. </details> <sub>Reviews (1): Last reviewed commit: ["ref(booklore): remove booklore since it ..."](https://github.com/dokploy/templates/commit/8af55b21f494f66bec6ac37a377c5a1d66a77127) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=27851459)</sub> <sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>  --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-06-02 06:09:51 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#9330