support journal-remote with SSH transport, without HTTP transport (dropping microhttpd dep)
Open
Nobody has claimed this yet.
journal-remote
RFE 🎁
- Dominant language
- C
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 140
Description
RFE
I have been thinking of how to drop off the micro http dependency of journald-remote. In fact I have been thinking of how to drop any web server dependency.
Has there been any discussion of connecting journald-upload to journald-remote with ssh?
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 reading the journald-upload and journald-remote entry points and investigating how their current HTTP and microhttpd dependency are connected. Determine the design needed for an SSH transport without HTTP; done means the services can communicate over SSH and the web-server dependency is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100