ResourceService doesn't start LogService
Open
Nobody has claimed this yet.
rs
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
Is there any reason why it shouldn't? (It's currently hard-coded not to).
If you want to start LogService yourself, you can.
If you don't want LogService at all, you can remove it from cms.conf.
(Motivated by the desire for an init script to just be able to start one program - cmsResourceService).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the ResourceService startup entry point and the cms.conf handling for LogService. Confirm how the current hard-coded exclusion works and whether service removal is supported by configuration; done means starting cmsResourceService also starts LogService by default while allowing it to be disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100