00:00 <XgF> asheesh: RookBoom needs to connect to an Exchange server

00:33 <asheesh> XgF: Yeah - insert powerbox here, in my imagination.

00:33 <asheesh> I was thinking about it because my girlfriend's office uses Exchange and could totally use this.

00:33 <asheesh> I think my friends at Akamai could too.

01:08 <mrdomino> so, i'm looking at the wildcard-ssl and static-hosting uh, situation

01:11 <mrdomino> am i correct in summarizing the current situation, for a sandcats user, as: "in order to expose a static site over https, I need to get my own wildcard cert (i.e. probably wait for letsencrypt to support it)"?

01:12 <mrdomino> i would not mind being able to do a, say, blog.mrdomino.sandcats.io redirect, but i think that's not currently possible

01:13 <mrdomino> oh, or i suppose i could get a non-wildcard letsencrypt cert, configure nginx to use it, and reverse-proxy on that domain specifically, yeah?

01:31 <kentonv> mrdomino: yeah you need some sort of reverse-proxy to apply SSL to a web-publishing domain. Does not need wildcard, though.

01:32 <mrdomino> b

01:32 <mrdomino> thanks

02:16 <asheesh> mrdomino: re: let's encrypt static publishing: we/I/you could totally integrate that into Sandstorm.

02:16 <asheesh> I think that'd be pretty swell.

02:16 <mrdomino> ooooh yeah

02:16 <mrdomino> nice-sized project too, from the sounds of it

02:16 <asheesh> Yeah - I can point you/anyone/me to all the right places in the code to do that.

02:16 <asheesh> Doubly so since I wrote most of that.

02:17 <mrdomino> all right. i've got a week of freedom coming up in like a month. it might be good to have contacts in place in time for it.

02:20 <asheesh> In theory another person was interested in working on that, too.

03:04 <asheesh> sandah: Let me know how that worked for you!

04:04 <asheesh> zarvox: I will read it!

09:39 <elimisteve> mrdomino: if you're talking about self-hosting Sandstorm and you're looking for a free SSL wildcard cert, Sandstorm now provides that for free! https://sandstorm.io/news/2015-10-01-free-ssl-certificates

09:40 <elimisteve> asheesh: when I package a Go app for Sandstorm, do I include the source and a build script, or do I include the binary?

10:39 <zarvox> elimisteve: include the binary in the spk; the source and a build script in your source repository.

10:39 <zarvox> If you're using vagrant-spk, your .sandstorm/build.sh would be the appropriate place to run the build script, and .sandstorm/launcher.sh would be the right place to launch the binary you built

22:02 <simonv3> asheesh: instead of derailing https://github.com/sandstorm-io/sandstorm/issues/1525#issuecomment-183979647 any more, I’ll continue asking here! As a user, since there’s no limit to what apps I can “install” (is there?), but rather to how many grains I can have (and how much space each one takes up) I’m wondering why I even need to “install” an

22:02 <simonv3> app first. Sure it allows me to create grains, but what’s the benefit (to me) of adding that extra step of installing the app?

22:02 <simonv3> Is it security? (the conscious “I can verify where this app comes from, who the author is, how trustworthy they are”)

22:03 <kentonv> simonv3: A couple things. First, during the install step you get to verify the author signature. Second, the installed app does take up space on your drive, so there is a limit to how many you could install.

22:09 <simonv3> kentonv: thanks, I’m not sure whether this is an issue beyond me trying to figure out how it works. I think “installing” an app make sense and it’s probably a well enough understood pattern for a lot of people. I was just wondering how far it was actual installation and how far it was a metaphor and actually an aspect of it’s implementation

22:14 <kentonv> simonv3: In a lot of cases, it's a metaphor. E.g. on Oasis, the app is almost always installed already, so "installing" really just flips a bit in the database to say that you specifically have "installed" it. (That's why it's instantaneous.)

22:14 <kentonv> but when the server doesn't already have the app then it does in fact download and unpack at "install" time

22:27 <chilts> ahah, that also (now) makes sense to me too!

22:27 <chilts> thanks for asking simonv3, I'd also been wondering