I'm glad to hear that Hetzner unblocks it; AWS hard-refuses to, and DigitalOcean only unblocks it for very large and well-established customers
I'll get back to you on the rest, I think I can…
we're probably not the only ones who'd like to use it, I am all for giving it its own flake
sigh I'm the one who wrote it, with Jade's help. currently there is no sort of autodeploy, and the file isn't checked in anywhere (I have a copy, and also there's the live copy). this is bad,…
oh!!!!! I had just assumed we'd use one of the cloud providers like Mailgun or Amazon SES, but since we're going to have actual commercial access, our outbound port 25 won't be blocked so we can…
oh yes, that really should be much, much clearer. thanks very much for reporting it.
hi! thanks for sending this. can you explain more about the motivation? I'm not personally familiar with detsys-ts, nor with how stable the branch you'd like to move it to is
yeah I think you're right, on closer read (I find it hard to see the context of changes on forgejo, but oh well)
good. yes. trailing whitespace bothers me beyond reason. please merge this.
yes, I agree with that caveat. also, we should still mention the existence of the module, right?
yes absolutely, sounds great, go ahead and merge it (fix that conflict of course)
Huh. Thank you. I think I understand how my test case wound up not hitting that... I had a lot of trouble at first separating out the builtin semantics from the chroot, since they both restrict…
That doesn't seem consistent with the tests I did last night, but it's possible that I wasn't testing in a way that drew out the actual behavior. At any rate I think there's more than enough…
oh. huh. interesting... so the two concepts of pure evaluation are different. drat :) but that makes sense.