<simonv3>
I’ll probably be using process.env.SANDSTORM for quick-survey
<simonv3>
there the whole permissions / sharing thing is pretty important, and I’ve been trying to get that right
<asheesh>
Cool (-:
jacksingleton has quit [Ping timeout: 240 seconds]
<Jan\>
hey whoever packaged wordpress needs to redo it with a stable version
<asheesh>
Are you experiencing a bug that seems likely to be occurring because of the version?
asmyers has joined #sandstorm
<Jan\>
well it breaks some plugins/themes
<Jan\>
because the alpha version isn't suported
<dwrensha>
Jan\: I suspect the reason for the breakage isn't the alpha version
<dwrensha>
unfortunately, there are lots of reasons that plugins might not work in the Sandstorm Wordpress package...
asmyers has quit [Ping timeout: 250 seconds]
<dwrensha>
for example, some plugins assume that the database is MySQL, while the Sandstorm package uses sqlite
<dwrensha>
or some plugins make overly strong assumptions about directory structure
<zarvox>
asheesh: I think we should avoid telling people to leave "autopublish" and "insecure" enabled, since it means that they can't have separate roles for the app later on without fixing their architecture to check roles/permissions
<zarvox>
it's true that it's not unsafe if used only with things that never grow roles or have any further granularity of privilege beyond the grain, but I think we do people a disservice by telling them "oh yeah you don't need that" and then later "well, actually we lied..."
funwhilelost has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
jacksingleton has joined #sandstorm
<asheesh>
zarvox: Sensible enough!
<asheesh>
dwrensha: Perhaps the WordPress package should move to MySQL now that that's easier than it used to be.
<asheesh>
TODO(eventually) etc.
home has joined #sandstorm
<dwrensha>
asheesh: in what sense is it now easier?
<dwrensha>
the problem with MySQL is the slow startup time and the tens of megabytes of overhead. I don't think we've solved those problems yet.
<dwrensha>
... but perhaps we've learned that those issues are worth putting up with in order to achieve a higher level of compatibility
<asheesh>
Yeah, I mean "easier" in that (I think?) before vagrant-spk has some scripts it can give you that start MySQL; I agree on the rest.
<asheesh>
erm I changed my mind about how to phrase that mid-sentence
<asheesh>
Yeah, I mean "easier" in that vagrant-spk has some scripts it can give you that start MySQL; at least those are in a clear place now, which is what is "easier". I agree on the rest.
<dwrensha>
yeah, vagrant-spk could definitely make the packaging nicer
<zarvox>
\o/
<Jan\>
sandstorm uses SQLite right ?
<asheesh>
WordPress on Sandstorm uses sqlite, yeah.
<asheesh>
(at the moment; you could create your own WordPress package if you were into that)
isd has joined #sandstorm
home has quit [Quit: Leaving]
asmyers has joined #sandstorm
funwhilelost has joined #sandstorm
simonv3 has quit [Quit: Connection closed for inactivity]
asmyers has quit [Ping timeout: 240 seconds]
isd has quit [Ping timeout: 265 seconds]
zarvox has quit [Ping timeout: 250 seconds]
larjona_ has quit [Ping timeout: 250 seconds]
dlitz has quit [Ping timeout: 250 seconds]
aldeka has quit [Ping timeout: 250 seconds]
ragesoss has quit [Ping timeout: 250 seconds]
aldeka_ has joined #sandstorm
larjona has joined #sandstorm
ragesoss has joined #sandstorm
dlitz has joined #sandstorm
zarvox has joined #sandstorm
mnutt__ has quit [Quit: mnutt__]
jadewang has quit [Remote host closed the connection]
isd has joined #sandstorm
mnutt__ has joined #sandstorm
decipherstatic has quit [Remote host closed the connection]
decipherstatic has joined #sandstorm
jadewang has joined #sandstorm
dlitz has quit [Ping timeout: 240 seconds]
funwhilelost has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
funwhilelost has joined #sandstorm
dlitz has joined #sandstorm
funwhilelost has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<zarvox>
Also, it looks like the four things protected by the Permissions API ( http://w3c.github.io/permissions/ ) are all things that at first glance we could shim out and make work over postMessage()
<zarvox>
(as well as the Permissions API itself!)
<zarvox>
Maybe not the ServiceWorker part of Push Notifications. Hmm.
<jacksingleton>
hey hey
<jacksingleton>
just read https://github.com/sandstorm-io/sandstorm/issues/316 - which seems to imply that the long polling fallback when websockets is unavailable doesn't work on Sandstorm. ie Sandstorm requires websockets even if the app uses SockJS. is that correct?
<zarvox>
Hmmm, I thought that bug was that Sandstorm degrades to long-polling when websockets are broken, but apps that don't degrade might appear broken even though the shell "works"
<zarvox>
You make a good point though - it's weird that if long-polling were working, that Meteor apps wouldn't fall back to that cleanly, since Meteor is supposed to handle that for you
<jacksingleton>
Yeah what I'm seeing is the shell degrades to long polling and continues to work, but Meteor apps try to load then start the reload loop that was mentioned in 316
isd has quit [Quit: Leaving.]
<mnutt__>
would it be a bad idea for me to frankenstein the powerbox capnp demo + legacy-http-bridge into a sender + receiver pair that allow one grain to call (a limited subset of) another grain’s services via http?
<mnutt__>
I’ll probably end up doing something more specific, but I kept trying to generalize and wound up with that
<mnutt__>
I can imagine you’d run the server half and say “only allow GETs, prefix those with /api” and it would hit your app with http
funwhilelost has joined #sandstorm
<kentonv>
mnutt__: On the requesting side, you should actually request a UiView capability. The user can paste in a regular webkey, and then you get the UiView for the target grain. Ask for ApiSession as the session type and you get its regular HTTP API.
<kentonv>
mnutt__: and very soon we'll have a picker UI for this
<mnutt__>
kentonv: so the side that makes the request will end up with the offerer’s HTTP API?
<kentonv>
yeah
<kentonv>
is your offering end Davros in this case?
<kentonv>
or some new thing?
<mnutt__>
yes. I’d like to build a gallery app that shows files offered from Davros
<kentonv>
cool
<mnutt__>
ideally eventually this app would be invokable from davros (“view in gallery” or something)
funwhilelost has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<kentonv>
yeah so you can do this with no changes to Davros
<mnutt__>
then build a music app like ampache
<kentonv>
although if you wanted to, say, have the gallery app only get access to one folder then that's more complicated
<kentonv>
but let's punt on that to start
<mnutt__>
initially it could probably get access to everything, although yeah eventually that’d be nice
<kentonv>
eventually we will support a notion of non-main UiViews, where a single grain can actually export UiViews representing subsets of itself. In Davros you'd naturally use this to share folders without sharing the whole grain.
<kentonv>
and then that will "just work" with this approach to the gallery app
<mnutt__>
that’s really cool, I can imagine getting a lot of use out of that
<kentonv>
anyway, for now, yeah, have the gallery app do a powerbox request for a UiView capability. Using the current copy-paste powerbox, I believe you can fulfill this by pasting in a webkey.
<kentonv>
that is, a webkey created through the sandstorm UI or an offer template
<mnutt__>
when you say powerbox request for UiView capability, I call the postMessage API, receive the response, send it to my backend, and have it initiate the session via capnp?
<kentonv>
mnutt__: yeah, you'll get a token which on the back-end you can restore into a capnp UiView capability by calling SandstormApi.restore().
<mnutt__>
ok, great
<kentonv>
hmmmm looking at the code there's a chance we haven't actually implemented restore() correctly for UiViews
<kentonv>
that is specifically for the grain's main UiView
<kentonv>
if true presumably we'll fix that very soon since zarvox is actively working on making this use case work
<kentonv>
there's a temporary alternative, which is that you can use HackSessionContext.getUiViewForEndpoint() and directly give it a webkey
<kentonv>
in that case you aren't using powerbox request at all
<mnutt__>
ah
<kentonv>
but that code path isn't well-tested. It was added for use in Diaspora but we didn't finish that port.
<kentonv>
it might work, though
<kentonv>
I'd try the powerbox request path first, because the code you need to write for that is basically exactly what you'll eventually need anyway
<kentonv>
and then try HackSessionContext if you need a temporary hack
<mnutt__>
ok, sounds good. thanks for the help
<kentonv>
fwiw the place where I think code is missing is in restoreInternal() in core.js
<kentonv>
doesn't appear to have the path for a regular webkey pointing to the whole grain, only for specific inner objects.
ocdtrekkie has quit [Remote host closed the connection]
aldeka_ has quit [Remote host closed the connection]
jacksingleton has quit [Ping timeout: 240 seconds]
rhapsodhy has quit [Remote host closed the connection]
rhapsodhy has joined #sandstorm
<zarvox>
My understanding was that the with-UI powerbox request flow doesn't involve webkeys at all, but has owner: grain instead.
<zarvox>
Oh, I think I see what you mean. We don't handle the case with non-frontendref tokens that are not UiViews (no .objectId) and are also not child tokens (no parentToken).
<zarvox>
er, that are UiViews
aldeka has joined #sandstorm
ocdtrekkie has joined #sandstorm
ArcTanSusan has joined #sandstorm
<kentonv>
zarvox: right
jacksingleton has joined #sandstorm
<jadewang>
hello IRC friends
<jadewang>
is anyone here in Berlin?
ArcTanSusan has quit [Quit: ArcTanSusan]
jacksingleton has quit [Ping timeout: 260 seconds]
ArcTanSusan has joined #sandstorm
jadewang has quit [Remote host closed the connection]
ArcTanSusan has quit [Quit: ArcTanSusan]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 264 seconds]
bb010g has quit [Quit: Connection closed for inactivity]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 260 seconds]
preilly has quit [Excess Flood]
logbot__ has quit [Write error: Broken pipe]
ocdtrekkie has quit [Write error: Broken pipe]
TC01 has quit [Quit: No Ping reply in 180 seconds.]
preilly has joined #sandstorm
logbot___ has joined #sandstorm
preilly is now known as Guest4751
ocdtrekkie has joined #sandstorm
nwf has quit [Read error: Connection reset by peer]
TC01 has joined #sandstorm
nwf has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 276 seconds]
ocdtrekkie has quit [Write error: Broken pipe]
ocdtrekkie has joined #sandstorm
asmyers has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 265 seconds]
asmyers has quit [Remote host closed the connection]
asmyers has joined #sandstorm
xet7 has joined #sandstorm
asmyers has quit [Remote host closed the connection]
asmyers has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 276 seconds]
itscassa|away is now known as itscassa
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 260 seconds]
ArcTanSusan has joined #sandstorm
mnutt__ has quit [Quit: mnutt__]
ragesoss has quit [Ping timeout: 260 seconds]
ragesoss has joined #sandstorm
ArcTanSusan has quit [Quit: ArcTanSusan]
asmyers has quit [Ping timeout: 240 seconds]
jadewang has joined #sandstorm
asmyers has joined #sandstorm
mnutt__ has joined #sandstorm
asmyers has quit [Remote host closed the connection]
asmyers has joined #sandstorm
maurer is now known as IcyManipulator
IcyManipulator is now known as maurer
amyers has joined #sandstorm
asmyers has quit [Read error: Connection reset by peer]
<simonv3>
It has a docker image, so I imagine it shouldn’t be too hard?
<dwrensha>
pdehaye: the first problem to solve is DNS. Sandstorm needs a wildcard host. If your server is listening on 127.0.0.1, you could use *.local.sandstorm.io
<dwrensha>
or I've heard that sometimes even something like *.localhost can work, for some client configurations
<pdehaye>
i am not sure i understand
<pdehaye>
if i just want local installation, for myself only, i can ignore the sandcats.io registration?
<pdehaye>
i think i need to step back one step, and understand virtualbox/vagrant better
<dwrensha>
ah
<pdehaye>
i will come back later, no worries :) maybe in a week...
amyers has joined #sandstorm
<zarvox>
simonv3: you'd probably start by adapting what's in the Dockerfile to vagrant-spk's setup.sh, build.sh, and launcher.sh scripts
amyers has quit [Remote host closed the connection]
amyers has joined #sandstorm
<zarvox>
for instance, all the apt/go/mysql package installation probably belongs in setup.sh, building the program and the UI probably belongs in build.sh, and setting up a new mysql server and running docker-entry.sh or equivalent belongs in launcher.sh
funwhilelost has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
natea has joined #sandstorm
<zarvox>
You might have to adjust some paths via the config - sandstorm makes everything but /var and /tmp readonly inside the grain, for instance
<simonv3>
zarvox: cool, thanks
<simonv3>
I’m not sure I’ll get to it, but just wanted to gauge complexity