Document and provide examples of usage for the content scanner
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Start by reviewing the existing docs/ folder and the content scanner API to determine how clients are expected to consume it. Document the recommended homeserver integration, explain whether a reverse proxy is needed, and add configuration and usage examples covering the requested setups. Done means a newcomer can follow the tutorial and understand the supported approach.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
I'm having trouble understanding how the content scanner is supposed to be used (I'm fairly new to this, so apologies if I'm missing something obvious here). How is the API supposed to be consumed - are clients referring to it, do you put a reverse proxy in front of (your) homeserver that intercepts requests to media and passes them to the scanner, other approaches? I'm not sure what is possible and also what is recommended.
Describe the solution you'd like
Ideally there is documentation on how you can use this with a home server and an example conf in case something additional is required (on homeserver.yaml or a reverse proxy setup)
Describe alternatives you've considered
I considered trying this with a reverse proxy, though I still wanted to open this request for docs - if there are clarifying comments on the request, I can open a doc PR.
Additional context
Hope to have a tutorial and examples under docs/ folder.
- Dominant language
- Python
- Stars
- 25
- Forks
- 16
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 12
Contributor guide
No contributing guide indexed for this repository
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.
More from element-hq/matrix-content-scanner-python
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
element-hq/matrix-content-scanner-python#162 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
element-hq/matrix-content-scanner-python#78 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
element-hq/matrix-content-scanner-python#77 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in element-hq/matrix-content-scanner-python
Similar issues
-
area: harness bug status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Human-Agent-Society/reef#625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
learningequality/kolibri#15351 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Name consistency Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eellak/triplestore#65 · 1 comment ·