shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

[Phase 8] Long-term daemon config file (Approach A) #251

New Issue
Open
opened 2026-04-08 06:34:40 +02:00 by shoko · 0 comments
shoko commented 2026-04-08 06:34:40 +02:00
Owner
Copy Link

Problem

Currently the queue-daemon sources kugetsu-config.sh directly. For long-term maintainability and reusability, we want a standalone daemon config.

Solution

Create kugetsu-queue-daemon.conf as a shell script that:

  1. Sources kugetsu-config.sh for base configuration
  2. Overrides/extends with daemon-specific settings

This allows:

  • Daemon to be run standalone
  • Different daemon configs for different use cases
  • Easy testing without affecting main kugetsu config

Status

FUTURE - Lower priority, no immediate dependency

Files

  • skills/kugetsu/scripts/kugetsu-queue-daemon.conf (new file)

Related Issue

Parent: #235

## Problem Currently the queue-daemon sources kugetsu-config.sh directly. For long-term maintainability and reusability, we want a standalone daemon config. ## Solution Create kugetsu-queue-daemon.conf as a shell script that: 1. Sources kugetsu-config.sh for base configuration 2. Overrides/extends with daemon-specific settings This allows: - Daemon to be run standalone - Different daemon configs for different use cases - Easy testing without affecting main kugetsu config ## Status **FUTURE** - Lower priority, no immediate dependency ## Files - skills/kugetsu/scripts/kugetsu-queue-daemon.conf (new file) ## Related Issue Parent: #235
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#251
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?