I know about the CGI standard, but mine does things a little differently (executable files don't just render pages but also handle logging, access control, etc. when put in special positions within a directory), so I still think it was worth the afternoon i spent making it.
i thought it was neat how php lets you write your website's logic with the same directory tree pattern that clients consume it from, but i didn't want to learn php so i made my own, worse version
#!/bin/bash doesn't work on NixOS since bash is in the nix store somewhere, #!/usr/bin/env bash resolves the correct location regardless of where bash is
I've taken some precautions, it's running in a container as an unprivileged user and the only writable mount is the directory where make writes rendered pages, but i probably should move it into a vm if i want to be completely safe lol
my website's backend is made with bash, it calls make for every request and it probably has hundreds of remote arbitrary code execution bugs that will get me pwned someday, it's great
edit: to clarify, it uses a rust program i made to expose the bash scripts as http endpoints, i'm not crazy enough to implement http in bash
it behaves like a static file server, but if a file has the others-execute permission bit set it executes the file instead of reading it
it's surprisingly nice for prototyping since you can just write a cli program and it's automatically available over http too
It could, so while you're using it you should make sure you don't have anything sensitive onscreen.
If your desktop supports Wayland at all, you could switch to it while using Zoom, even if other things don't work as well, then switch back when you aren't.
Why did you photoshop the image to make his face bigger?