mnutt_ has quit [Read error: Connection reset by peer]
bemasc has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 265 seconds]
isd has joined #sandstorm
dwrensha has joined #sandstorm
jemc has quit [Ping timeout: 260 seconds]
jemc has joined #sandstorm
xet7_ is now known as xet7
jemc has quit [Ping timeout: 268 seconds]
jadewang has joined #sandstorm
jadewang has quit [Remote host closed the connection]
TimMc has quit [Read error: Connection reset by peer]
TimMc has joined #sandstorm
wew has joined #sandstorm
ThePurgingPanda has quit [Ping timeout: 252 seconds]
wolcen has quit [Ping timeout: 240 seconds]
afuentes has quit [Ping timeout: 240 seconds]
jemc has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Remote host closed the connection]
jadewang has joined #sandstorm
Telesight has quit [Quit: Leaving.]
Zertrin has quit [Remote host closed the connection]
Zertrin has joined #sandstorm
KooBaa has quit [Remote host closed the connection]
KooBaa has joined #sandstorm
KooBaa has quit [Ping timeout: 250 seconds]
dakrone has joined #sandstorm
<dakrone>
I've seen on a forum that sandstorm doesn't support being mapped at a path with Nginx proxy_pass, is that still accurate? Is there no way to map it to be https://example.com/sandstorm?
jemc has quit [Ping timeout: 244 seconds]
jemc has joined #sandstorm
<isd>
dakrone: Sandstorm makes pretty heavy use of subdomains, so I don't see how that would even work (or, at least, I don't know what it woud buy you)
KooBaa has joined #sandstorm
<dakrone>
isd: well, perhaps *.ss.example.com instead of *.example.com ?
<dakrone>
since I already run many different things behind nginx on my server, so I can't just let sandstorm take over everything
jemc has quit [Ping timeout: 260 seconds]
<isd>
dakrone: you should be able to put it on a subdomain, yeah.
<dakrone>
ah okay, so I can do that, that would be great
<isd>
I don't know about the nginx details, but that's the general route I would go
<isd>
all: is it possible, or even on the roadmap to be able to do fine-grained sharing of resources within a grain? Example: If I have a filesystem-ish app like davros, and I'd like to share a subdirectory with someone
<isd>
This seems like something that ought to be super easy with a capability approach /in general/, but from what I can tell you can't share objects with sandstorm (at least via the UI) at a granularity smaller than a grain, plus a parameter like read/write (fixed, finite types).
<isd>
I'm looking at things, and this seems like it would be major surgery to get working. Am I wrong?
<kentonv>
isd: We plan to support this eventually, by letting a grain export UiView capabilities other than the "main" one