Improve -S (built-in webserver) to support optional ca/crt/key arguments
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
This would be nice just because for somebody who just wants to run a simple PHP application in a Docker container and set it up behind Cloudflare; they little more than suggest that you establish end-to-end encryption and even provide you with a certificate bundle to use with your application. In general I prefer less complexity for anything that I actually have to maintain, so if at most all I have to run is 1 container (which serves the PHP application with php -S) then it's a much better deal for me than having to mess around with nginx, or apache.
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 PHP built-in webserver implementation and its handling of the -S option. Define how optional ca, crt, and key arguments should be accepted and verify that a PHP application can use them for HTTPS behind Cloudflare.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100