summaryrefslogtreecommitdiff
path: root/tests/lighttpd.conf (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Node.js -> GoEuAndreh2024-03-251-35/+0
|
* src/hero.mjs: Log to stdout instead of stderrEuAndreh2024-03-171-3/+3
| | | | | | | | | | | | | | | | | The first question that this brings is: Is the output of the program useful for a downstream process? Is this logging an *output* of the program? But in this case, the answer is: yes, for both questions. A downstream program could very well be fed the output of the program via a pipe and process it, as the data being emitted is meant to be ingested. So instead of following the default "warnings ought to go to stderr" model, we acknowledge that the data is actually an *out*put, and send it to std*out*.
* tests/lighttpd.conf: add the upgrade header without replacing existing onesEuAndreh2024-03-141-1/+1
|
* tests/lighttpd.conf: Forward "enable" header to allow connection upgradeEuAndreh2024-03-141-0/+3
|
* src/hero.mjs: Add rmIf() and mkfifo()EuAndreh2024-03-061-2/+2
|
* Setup user-level lighttpd reverse proxy for development and testingEuAndreh2024-03-011-0/+32
Add static files as in production, too.