i think what i actually want is :⁠—

• A GitWeb instance

• A number of users which only have git access, and only to repositories they own

• A straightforward means of getting new repositories (and corresponding subdomains) allocated to users [this can probably just be manual, on request]

• A post-receive hook in every repository which, if the repository has a file named Makefile or GNUmakefile, clones the repository and then runs `make install DESTDIR=public`, serving the contents of the resulting `public` directory from a corresponding subdomain

• Maybe a small amount of allowable additional server configurations besides

i have some good makefiles you can use; this gets you a lot

@Lady Makefile execution as a service is always scary, but https://codeberg.org/Codeberg/pages-server might get you there without a ton of effort if you can stomach Gitea over gitweb. (I assume you have your reasons for not doing Git{Hub, Lab} Pages, but obviously those also exist.)

@aschmitz oh i mean i would never give access to anyone i didn’t trust OR put anything sensitive on the server ever OR have any kind of uptime or reliability guarantees, if i were to ever do this, to be clear

for my own purposes, i just run make locally and then rsync. but i think that’s a tiny bit too unstructured to be a shared workflow

i think proper CI/CD pipelines with gitea/forgejo/gitlab/github etc are Fine, but wasteful, and also best to do on their infrastructure and not on a friend’s