轩辕镜像 官方专业版
轩辕镜像
专业版
轩辕镜像 官方专业版
轩辕镜像
专业版
首页个人中心搜索镜像
交易
充值流量¥7起我的订单
文档
工具
提交工单页面收录
kamiyomu

marcoscostadev/kamiyomu

marcoscostadev

KamiYomu lets manga fans read, download, store, and host their own private reader.

下载次数: 0状态:社区镜像维护者:marcoscostadev仓库类型:镜像最近更新:2 个月前
让 AI 帮你使用轩辕镜像? · 展开查看说明 · 点击收起说明

如果你使用 DeepSeek、元宝 AI、Copilot、ChatGPT 等 AI 工具,协助配置轩辕镜像、编写 docker pull 命令、修改 Docker Compose 镜像地址、配置镜像加速、排查镜像拉取失败、分析报错日志等问题,请先让 AI 阅读并遵守轩辕镜像的规则文档。

只需在 AI 对话中先发送下面这句话即可:

请先完整阅读并严格遵守以下文档中的全部规则与要求:

https://xuanyuan.cloud/agents.md

在未充分阅读并理解该文档前,不要生成任何命令、配置、修改建议、故障排查方案或技术回答。后续所有输出都必须严格以该文档中的规范为最高优先级执行。

查看 agents.md 用法指南与完整示范。国内用户首推 元宝 AI、DeepSeek 的深度思考模式,不推荐豆包 AI;Cursor 等编辑器可在对话 @ 该链接,或加入 User Rules。 若 AI 无法访问外链,可 打开说明文档 复制全文粘贴。文档会随站点更新,复制内容可能过期,建议定期检查。

镜像简介
下载命令
镜像标签列表与下载命令
轩辕镜像,加速的不只是镜像。
点击查看

KamiYomu — Your Self-Hosted Manga Crawler

!https://raw.githubusercontent.com/KamiYomu/KamiYomu/refs/heads/main/Inkscape/logo.svg

KamiYomu is a powerful, extensible manga crawler built for manga enthusiasts who want full control over their collection. It scans and downloads manga from supported websites, stores them locally, and lets you host your own private manga reader—no ads, no subscriptions, no limits.


✨ Features

  • 🔍 Automated Crawling
    Fetch chapters from supported manga sites with ease.

  • 💾 Local Storage
    Keep your manga files on your own server or device.

  • 🧩 Plugin Architecture
    Add support for new sources or customize crawling logic.

  • 🛠️ Built with .NET Razor Pages
    Lightweight, maintainable, and easy to extend.


🚀 Why KamiYomu?

Whether you're cataloging rare series, powering a personal manga dashboard, or seeking a cleaner alternative to bloated online readers, KamiYomu puts you in control of how you access and organize manga content. It’s a lightweight, developer-friendly crawler built for clarity, extensibility, and respectful use of publicly accessible sources. Content availability and usage rights depend on the licensing terms of each source — KamiYomu simply provides the tools.



Requirements

  • https://www.docker.com/get-started

📦 Getting Started

save the following docker-compose.yml file to run KamiYomu with Docker:

yml
services:
  kamiyomu:
    image: marcoscostadev/kamiyomu:latest # Check releases for latest versions
    ports:
      - "8080:8080" # HTTP Port
    environment:
        # List of Hangfire server identifiers available to process jobs.
        # Each name corresponds to a distinct background worker instance;
        # add more entries here if you want multiple servers to share or divide queues.
        # add more entries using incrementing indexes (e.g., Worker__ServerAvailableNames__1, Worker__ServerAvailableNames__2, etc.)
        Worker__ServerAvailableNames__0:   "KamiYomu-background-1" 
        

        # Queues dedicated to downloading individual chapters.
        # add more entries using incrementing indexes (e.g., Worker__DownloadChapterQueues__1, Worker__DownloadChapterQueues__2, etc.)
        Worker__DownloadChapterQueues__0:  "download-chapter-queue-1" 

        # Queues dedicated to scheduling manga downloads (manages chapter download jobs).
        # add more entries using incrementing indexes (e.g., Worker__MangaDownloadSchedulerQueues__1, Worker__MangaDownloadSchedulerQueues__2, etc.)
        Worker__MangaDownloadSchedulerQueues__0:  "manga-download-scheduler-queue-1" 

        # Queues dedicated to discovering new chapters (polling or scraping for updates).
        # add more entries using incrementing indexes (e.g., Worker__DiscoveryNewChapterQueues__1, Worker__DiscoveryNewChapterQueues__2, etc.)
        Worker__DiscoveryNewChapterQueues__0:  "discovery-new-chapter-queue-1" 

        # Specifies the number of background processing threads Hangfire will spawn.
        # Increasing this value allows more jobs to run concurrently, but also raises CPU load 
        # and memory usage.
        # Each worker consumes ~80 MB of memory on average while active 
        # (actual usage may vary depending on the crawler agent implementation and system configuration).
        Worker__WorkerCount: 1

        # Defines the maximum number of crawler instances allowed to run concurrently for the same source.
        # Typically set to 1 to ensure only a single crawler operates at a time, preventing duplicate work,
        # resource conflicts, and potential rate‑limiting or blocking by the target system.
        # This value can be increased to improve throughput if the source supports multiple concurrent requests.
        #
        # Note:
        # - Worker__WorkerCount controls the total number of threads available.
        # - Worker__MaxConcurrentCrawlerInstances limits how many threads can be used by the same crawler.
        #
        # Examples:
        # - If Worker__MaxConcurrentCrawlerInstances = 1 and Worker__WorkerCount = 4,
        #   then up to 4 different crawler agents can run independently.
        # - If Worker__MaxConcurrentCrawlerInstances = 2 and Worker__WorkerCount = 6,
        #   then each crawler agent can run up to 2 instances concurrently,
        #   while up to 3 different crawler agents may be active at the same time.
        Worker__MaxConcurrentCrawlerInstances: 1

        # Minimum delay (in milliseconds) between job executions.
        # Helps throttle requests to external services and avoid hitting rate limits (e.g., HTTP 423 "Too Many Requests").
        Worker__MinWaitPeriodInMilliseconds: 3000

        # Maximum delay (in milliseconds) between job executions.
        # Provides variability in scheduling to reduce the chance of IP blocking or service throttling.
        Worker__MaxWaitPeriodInMilliseconds: 9001

        # Maximum number of retry attempts for failed jobs before marking them as permanently failed.
        Worker__MaxRetryAttempts: 10

        # Default language for the web interface (e.g., "en", "pt-BR", "fr").
        UI__DefaultLanguage: "en" 
    restart: unless-stopped
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8080/healthz"]
      interval: 30s
      timeout: 10s
      retries: 3
    volumes:
      - ./AppData/manga:/manga # Your desired local path for manga storage
      - Kamiyomu_database:/db
      - kamiyomu_agents:/agents
      - kamiyomu_logs:/logs

volumes:
  kamiyomu_agents:
  Kamiyomu_database:
  kamiyomu_logs:

In the folder where you saved the docker-compose.yml file, run:

bash
    docker-compose up -d

You will have access to the web interface at http://localhost:8080. Keep in mind to map the volumes to your desired local paths. See the releases branchs for identifying the versions available.

Configure your sources and crawler agents

Download crawler agents from NuGet Package from https://github.com/orgs/KamiYomu/packages and upload them in http://localhost:8080/Settings/CrawlerAgents.

🛠️ Development Setup

We recommend using Visual Studio 2022 or later with the .NET 8 SDK installed. However, you can also run KamiYomu using VsCode.

  1. Fork the repository
  2. Select the develop branch (git checkout develop)
  3. Create your feature branch (git checkout -b feature/AmazingFeature)
  4. Commit your changes (git commit -m 'Add some AmazingFeature')
  5. Push to the branch (git push origin feature/AmazingFeature)
  6. Open a Pull Request against the develop branch

Using Visual Studio

  • Docker: https://www.docker.com/get-started
  • Visual Studio: Download here
  • .NET 8 SDK: Download here
  1. Clone the repository
    bash
    git clone https://github.com/KamiYomu/KamiYomu.Web.git
    
  2. Open the solution in Visual Studio in /src/KamiYomu.Web.sln
  3. Set docker-compose project as startup project (Right-click on project, select Set As Startup Project.).
  4. Run it

Using VsCode

To get started with local development using Visual Studio Code, ensure the following tools are installed:

Required Tools

  • Docker: https://www.docker.com/get-started
  • Visual Studio Code https://code.visualstudio.com/
  • C# Dev Kit Extension https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit
  • Docker Extension for VS Code https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-docker

Note: Make sure Docker is installed and running on your machine.

  1. Clone the Repository
bash
    git clone https://github.com/KamiYomu/KamiYomu.Web.git
  1. Running the Project in VS Code
  • Open the ./src/ folder in VS Code.
  • Navigate to the "Run and Debug" tab (Ctrl+Shift+D) or press F5.
  • Select the launch configuration: "Attach to .NET Core in Docker".
  • Click the ▶️ Start Debugging button.

This project includes predefined tasks to build and run the Docker container automatically. If you install all required extensions, the project will run and open the browser in http://localhost:8080

NOTE: You may see a window with some error related => ERROR [kamiyomu.web internal] load metadata for mcr.microsoft.com/dotnet/sdk:8.0, just click on abort button then try again.

🧩 Create your First Crawler Agent

To create your first crawler agent, follow these steps:

  1. Set Up a New Project: Create a new Class Library project in Visual Studio or your preferred IDE.
  2. Add References: Add references to the necessary KamiYomu packages from NuGet KamiYomu.CrawlerAgents.Core.
  3. Implement the 5 methods from ICrawlerAgent Interface: Create a class that implements the ICrawlerAgent interface. This class will contain the logic for crawling a specific manga source.
csharp

/// <summary>
/// Defines a contract for manga crawling agents that support search, retrieval, and metadata extraction.
/// </summary>
public interface ICrawlerAgent : IDisposable
{
    /// <summary>
    /// Asynchronously retrieves the favicon URI associated with the crawler's target site.
    /// </summary>
    /// <param name="cancellationToken">Optional token to cancel the operation.</param>
    /// <returns>A <see cref="Task{Uri}"/> representing the favicon location.</returns>
    Task<Uri> GetFaviconAsync(CancellationToken cancellationToken);

    /// <summary>
    /// Searches for manga titles matching the specified name, using either traditional pagination or a continuation token.
    /// </summary>
    /// <param name="titleName">The title or keyword to search for.</param>
    /// <param name="paginationOptions">Pagination parameters, supporting both page-based and continuation token-based pagination.</param>
    /// <param name="cancellationToken">Optional token to cancel the operation.</param>
    /// <returns>A paged result containing a collection of matching <see cref="Manga"/> entries.</returns>
    Task<PagedResult<Manga>> SearchAsync(string titleName, PaginationOptions paginationOptions, CancellationToken cancellationToken);

    /// <summary>
    /// Retrieves detailed information about a specific manga by its unique identifier.
    /// </summary>
    /// <param name="id">The unique ID of the manga.</param>
    /// <param name="cancellationToken">Optional token to cancel the operation.</param>
    /// <returns>A <see cref="Task{Manga}"/> containing the manga details.</returns>
    Task<Manga> GetByIdAsync(string id, CancellationToken cancellationToken);

    /// <summary>
    /// Retrieves a paged list of chapters for the specified manga.
    /// </summary>
    /// <param name="manga">The manga object.</param>
    /// <param name="paginationOptions">Pagination parameters, supporting both page-based and continuation token-based pagination.</param>
    /// <returns>A paged result containing a collection of <see cref="Chapter"/> entries.</returns>
    Task<PagedResult<Chapter>> GetChaptersAsync(Manga manga, PaginationOptions paginationOptions, CancellationToken cancellationToken);
    /// <summary>
    /// Retrieves the list of page images associated with a given manga chapter.
    /// </summary>
    /// <param name="chapter">The chapter entity containing metadata and identifiers.</param>
    /// <param name="cancellationToken">Optional token to cancel the operation.</param>
    /// <returns>A collection of <see cref="Page"/> objects representing individual chapter pages.</returns>
    Task<IEnumerable<Page>> GetChapterPagesAsync(Chapter chapter, CancellationToken cancellationToken);
}
  1. Build the Project: Compile your project to generate the DLL file.
  2. Deploy the Crawler Agent: Upload the compiled DLL to the KamiYomu web interface under the "Crawler Agents" section. Or publish the package in NuGet.Org
  3. Configure and Use: Once uploaded, configure the crawler agent in KamiYomu and start crawling manga from the supported source.

Do you want a reference implementation? Check:

  • https://github.com/KamiYomu/KamiYomu.CrawlerAgents.MangaDex if you crawler will consume a web api.
  • https://github.com/KamiYomu/KamiYomu.CrawlerAgents.MangaKatana if you crawler will consume a web page.
  • https://github.com/KamiYomu/KamiYomu.CrawlerAgents.MangaFire another example to consume a web page.

NOTE: Make sure to use a Validator console app to ensure your crawler agent meets all requirements before deploying it to KamiYomu.

*** using this <PropertyGroup> in your csproj, adjust the title accorgly

xml
	<PropertyGroup>
		<Title>My Crawler Agent</Title>
		<Description>A dedicated crawler agent for accessing public data from My Personal Stuff. Built on KamiYomu.CrawlerAgents.Core, it enables efficient search, metadata extraction, and integration with the KamiYomu platform.</Description>
		<Authors>MyName</Authors>
		<Owners>MyName</Owners>
		<PackageProjectUrl>https://github.com/MyProjectUrl</PackageProjectUrl>
		<RepositoryUrl>https://github.com/MyRepositoryUrl</RepositoryUrl>
		<RepositoryType>git</RepositoryType>
		<PackageTags>kamiyomu-crawler-agents;manga-download</PackageTags>
		<PackageLicenseExpression>GPL-3.0-only</PackageLicenseExpression>
		<Copyright>© Personal. Licensed under GPL-3.0.</Copyright>
		<PackageIconUrl>https://raw.githubusercontent.com/MyPackageLogoUrl</PackageIconUrl>
		<PackageIcon>Resources/logo.png</PackageIcon>
		<PackageReadmeFile>README.md</PackageReadmeFile>
	</PropertyGroup>

The Package Tag <PackageTags>kamiyomu-crawler-agents</PackageTags> is required to be showed in KamiYomu add-ons See the existing projects to use as a reference for your csproj.

Debugging Your NuGet Package in KamiYomu

This guide explains how to build, import, and debug a NuGet package for use in KamiYomu.


1. Configure Your Project

Add the following snippet to your .csproj file.
This ensures that a NuGet package is generated during the Debug build:

xml
<PropertyGroup Condition="'$(Configuration)' == 'Debug'">
  <GeneratePackageOnBuild>True</GeneratePackageOnBuild>
  <IncludeSymbols>True</IncludeSymbols>
  <IncludeSource>True</IncludeSource>
  <SymbolPackageFormat>snupkg</SymbolPackageFormat>
</PropertyGroup>

2. Build the Project

Run a build in Debug mode.
The generated NuGet package (.nupkg) and symbol file (.pdb) will be located in:

3. Import the Package into KamiYomu

  1. Open KamiYomu.
  2. Navigate to Crawler Agents in the menu.
  3. Import your NuGet package (.nupkg) from the ***/Debug folder.

4. Copy the Symbol File

Copy the .pdb file from your ***/Debug folder into:

src\AppData\agents\{your-crawler}\lib\net8.0

This allows Visual Studio to map your source code during debugging.

5. Debugging in KamiYomu

KamiYomu uses a decorator class to invoke agent methods:

src\KamiYomu.Web\Entities\CrawlerAgentDecorator.cs

  • Set a breakpoint in any call within this class.
  • When Visual Studio hits the breakpoint, step into the call.
  • Your agent’s source code will be displayed and debuggable.

🧠 Tech Stack- .NET 8 Razor Pages

  • Hangfire for job scheduling
  • LiteDB for lightweight persistence
  • HTMX + Bootstrap for dynamic UI
  • Plugin-based architecture for source extensibility

📜 License

This project is licensed under AGPL-3.0. See the LICENSE file for details.

🤝 Contributing

Pull requests are welcome! If you have ideas for new features, plugin sources, or UI improvements, feel free to open an issue or submit a PR.

💬 Contact

Questions, feedback, or bug reports? Reach out via GitHub Issues or start a discussion.

镜像拉取方式

您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。

轩辕镜像加速拉取命令点我查看更多 kamiyomu 镜像标签

docker pull docker.xuanyuan.run/marcoscostadev/kamiyomu:<标签>

使用方法:

  • 登录认证方式
  • 免认证方式

DockerHub 原生拉取命令

docker pull marcoscostadev/kamiyomu:<标签>

轩辕镜像配置手册

按平台快速找到配置文档

一键安装

一键安装 Docker

Linux Docker 一键安装

AI

用 AI 使用轩辕镜像

agents.md · AI 对话 · 提示词

Docker

登录仓库拉取

登录认证 · 私有仓库

专属域名拉取

免登录 · 高速拉取

Linux

Docker 镜像配置

Windows / Mac

Docker Desktop 配置

MacOS OrbStack

OrbStack 容器

Apple Container

macOS 原生容器

Docker Compose

Compose 项目配置

NAS

群晖

Synology 配置

飞牛

fnOS 镜像配置

绿联

绿联 NAS

威联通

QNAP 配置

极空间

极空间 NAS

Unraid

Unraid NAS

企业仓库

其他仓库

ghcr · Quay · nvcr

Harbor 镜像源

Proxy Repository 对接

Portainer 镜像源

Registries 配置

Nexus 镜像源

Docker Proxy 缓存

开发工具

Dev Containers

VS Code 开发容器

Podman

Podman 配置指南

Singularity / Apptainer

HPC 科学计算容器

Kubernetes

K8s Containerd

Kubernetes · Containerd

K3s

轻量级集群

面板 / 网络

爱快路由

iKuai 镜像加速

宝塔面板

一键配置镜像源

需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单

镜像拉取常见问题

功能

版本功能对比

功能对比 · 版本选择

支持的镜像仓库

Docker Hub · GCR · GHCR

新手拉取配置

登录 · 专属域名 · 配置

docker search 限制

专属域名 · Hub 搜索

不支持 push

仅支持 pull · 不支持

拉取速度原因

带宽 · 缓存 · 冷热镜像

错误码

402 与流量用尽

402 · 流量包 · 充值

401 认证失败

401 · docker login

manifest unknown

标签错误 · 镜像不存在

410 Gone 排查

410 · Docker 升级

429 限流

免费版 · 专业版 · 企业版 · 请求频率

其他报错

DNS 超时

DNS 解析 · 网络超时

TLS 证书失败

no matching manifest(架构)

账号

失败是否计费

manifest · blob · 计费

申请开发票(企业 / 个人)

企业 · 个人 · 工单

修改登录密码

网站 · 仓库 · 重置

注销账户

工单 · 数据 · 注销

原理

mirrors 不生效

daemon.json · 重启

去掉域名前缀

docker tag · 重命名

指定架构拉取

ARM64 · AMD64 · 多架构

latest 与「最新」

digest · 版本号 · 标签

查看全部问题→

用户好评

来自真实用户的反馈,见证轩辕镜像的优质服务

用户头像

oldzhang

运维工程师

Linux服务器

5

"Docker访问体验非常流畅,大镜像也能快速完成下载。"

轩辕镜像
镜像详情
...
marcoscostadev/kamiyomu
教程轩辕镜像功能与使用教程
定价查看流量套餐与价格
热门查看热门 Docker 镜像推荐
博客Docker 镜像公告与技术博客
专业版 · 高速稳定拉取镜像
高速镜像下载·在线技术支持·99.95% SLA 保障·付费会员免广告
50GB 仅 ¥7/年
专业版 · 高速稳定拉取镜像
50GB 仅 ¥7/年
高速镜像下载·在线技术支持·99.95% SLA 保障·付费会员免广告
用户协议·隐私政策·增值电信业务经营许可证:浙B2-20261007·©2024-2026 源码跳动©2024-2026 杭州源码跳动科技有限公司·商务合作:点击复制邮箱