<paulproteus>
Yayyyy I'm beginning to be able to use the GlobalSign SOAP API!
gopar has quit [Quit: Leaving]
<paulproteus>
The SOAP options in JS-land don't seem as good as the ones in Python-land.
<zarvox>
"time to port sandcats to Python"
isd has quit [Remote host closed the connection]
<XgF>
paulproteus: The fact that you're using SOAP scares me
<XgF>
paulproteus: When did Sandcats become all enterprisey?
<paulproteus>
XgF: Well, I don't want to go into huge depth for fear of implying promises, but I'm integrating with a GlobalSign service.
<paulproteus>
That's probably unnecessarily obtuse. You probably have caught wind in e.g. Hacker News comments by kentonv that we periodically say we're trying to see if we can work with CAs to get auto-configured HTTPS for self-hosting Sandstorm users.
<paulproteus>
This is related to that.
<paulproteus>
But don't construe this to be a promise that it'll actually work out, when it'll work out.
<tarabkoferko>
hah, firewall, will check that, thanks
<paulproteus>
If you can give me the domain name, I can see if there's something I can figure out.
<paulproteus>
Also "obviously" I should make an online interactive troubleshooting guide, hmm!
<kentonv>
probably the installer script should include a reminder that you'll need to open the port
<paulproteus>
My hope was that we could do that automatically so that if things are already working we don't bother you.
<kentonv>
yes, I was about to say -- the sandcats server could attempt to call back
<dwrensha>
nightwatch gotcha: waitForElementVisible("li[name=value]") works, but waitForElementVisible("li[name='value']") does not.
<kentonv>
wat
<kentonv>
surely it uses document.querySelector()?
<dwrensha>
i dunno
<paulproteus>
kentonv: I wonder what your opinion is of having things be a little less polished and vertically integrated but still working. e.g. I could rely on portchecktool.com instead of adding code to the Sandcats service.
<Walkproteus>
There are a lot of good ways to help out the sandstorm project, some of them in no particular order are
<Walkproteus>
You can help other people start using sand storm. You can do this from your own server, by inviting the people, or by having them think about pre ordering our managed hosting.
<Walkproteus>
You can package app for sandstorm which makes them available to all tense from users. Its really amazing how high leverage this is. Something that's useful to you might be useful to somebody else, and so if you share the package, anybody else can get those benefits.
<Walkproteus>
...all users, even the ones that aren't tense....
Walkproteus has quit [Client Quit]
Walkproteus2 has joined #sandstorm
<Walkproteus2>
Anyway. Can say more with fewer typos in a few min.
<paulproteus>
An example of an email people send before doing a mass bug filing in Debian.
<neynah>
! tyvm
<paulproteus>
In our case, all packages are affected, so it's not like we can show a list like this and have it be useful.
<paulproteus>
But the text here might be useful to understand the idea.
<paulproteus>
https://fedoraproject.org/wiki/Mass_bug_filing is a more verbose document about Fedora (another Linux distro, approximately the same thing as Debian from your perspective) about the same concept.
<paulproteus>
I guess if you want to get really fancy, you could submit a pull request containing the required changes to their sandstorm-pkgdef.capnp.
<paulproteus>
But it's probably fine to give people clear instructions on what to change in their sandstorm-pkgdef.capnp and give them the files to add.