coyotebush has quit [Quit: No Ping reply in 180 seconds.]
coyotebush has joined #sandstorm
Telesight has quit [Remote host closed the connection]
xet7 has quit [Remote host closed the connection]
xet7 has joined #sandstorm
jemc has joined #sandstorm
Telesight has joined #sandstorm
afuentes has joined #sandstorm
digitalcircuit has quit [Quit: Signing off from Quassel - see ya!]
<TimMc>
crw: Yep, that work is still pending.
digitalcircuit has joined #sandstorm
<TimMc>
I should see about setting up wildcard LE certs for my nginx...
jemc has quit [Read error: Connection reset by peer]
<kentonv>
crw, I know dwrensha has gotten his Sandstorm set up with a Let's Encrypt wildcard. Unfortunately it doesn't look like Sandstorm will be able to do much to automate it, since you have to pass a DNS challenge.
ogres has joined #sandstorm
samba_ has joined #sandstorm
samba_ has quit [Ping timeout: 240 seconds]
samba_ has joined #sandstorm
_whitelogger has joined #sandstorm
Telesight has quit [Quit: Leaving.]
isd has joined #sandstorm
afuentes has quit [Ping timeout: 240 seconds]
xet7 has quit [Quit: Leaving]
<ccx^xmpp>
Can't you at that point just any ACMEv2 client, assuming Sandstorm detects certificate files changing and reloads?
<kentonv>
ccx^xmpp, not sure what you mean. You probably need to put nginx in front of Sandstorm to do the TLS termination, and then arrange for Let's Encrypt to deliver certs to nginx
<kentonv>
Sandstorm could be doing the termination, but that just changes things so you have to deliver the certs to Sandstorm. What Sandstorm cannot do is automatically request the certs for you, because you have to pass a DNS challenge, and Sandstorm doesn't have access to your DNS
<kentonv>
(unless you are on sandcats, in which case we're already providing you with TLS certs)
<kentonv>
ocdtrekkie, regarding your "last used" bug: is it consistent with the last-used time only being updated if you keep the grain open for at least a minute?
<ocdtrekkie>
It seems relatively plausible to me, kentonv. I do a lot of short updates on documents.
<ocdtrekkie>
Though I didn't think Sandstorm closed them again within a minute?
<ocdtrekkie>
Once I noticed some of my docs didn't show a recent date of course, I tested by noticing that opening grains didn't move them to the top of the list, which again, would be "less than a minute" of testing in most cases.
<ocdtrekkie>
Yeah, that seems to be the case.
<coffeebird[m]>
is it possible to buik download grain backups?
<ocdtrekkie>
coffeebird[m]: Sadly, no, not at present, AFAIK.
<kentonv>
ocdtrekkie, yeah, pretty sure that was the bug. Pushing a Sandstorm release now to fix. Debating whether or not I want to bother updating Oasis...
<kentonv>
(nothing else has changed since last release)
<ocdtrekkie>
I need to review some apps.
<ocdtrekkie>
Things not jumping to the top is mildly irritating sometimes, but not a huge issue.
<kentonv>
guess I could push a hotfix... if it gets reverted by accident it's not going to be outage-inducing, at least