11:07 <theSoenke> hi. i'm currently trying to package https://github.com/thelounge/lounge for sandstorm and have an issue. when i make the app available with vagrant-spk dev i can create a grain in sandstorm, but the grain shows just a loading animation forever. maybe someone has a hint what i might have done wrong. here is the code https://github.com/theSoenke/lounge

11:20 <asheesh> theSoenke: Hi! https://docs.sandstorm.io/en/latest/developing/troubleshooting/ can be useful sometimes

11:21 <asheesh> You can also try to open the grain log in the top bar, see https://docs.sandstorm.io/en/latest/using/top-bar/

11:23 <theSoenke> thanks. the grain log looks helpful. seems like the node applications is crashing

11:25 <asheesh> Sometimes it crashes due to using 'localhost', whereas we remove /etc/hosts within the sandbox, so you can use '127.0.0.1' instead where you might otherwise use 'localhost'.

11:26 <theSoenke> the issues seems to be that it can't create the directory /opt/app/.lounge

11:28 <asheesh> Ah hah. "Only the /var directory is writable; the rest of the filesystem (which contains the contents of your app package) is read-only." <https://docs.sandstorm.io/en/latest/developing/troubleshooting/>

11:28 <asheesh> https://docs.sandstorm.io/en/latest/vagrant-spk/services/ "Create what you need in /var. Each Sandstorm grains runs with an empty, fresh /var at grain creation time, so you'll have to ensure that any necessary directories or files are created in launcher.sh."

11:30 <asheesh> AFK a little bit; I'm asheesh@sandstorm.io if you need more help but I'm not on IRC then!

11:32 <theSoenke> ok. thanks for your help. will try to find a solution to store the data in /var

11:40 <reisi> just to make sure i'm not doing this unnecessarily hard, if i want to change c++ or js files and test them out manually it's best to run make fast && sudo make update?

11:51 <reisi> ekam seems to eagerly re-build everything on every c++ file change, and this of course takes a lot of time. not sure how make continuous integrates and make update play together

12:13 <reisi> keeping "make continuous" running then attemping "make fast" fails, so it's not supposed to be used like this at least

12:27 <reisi> more questions, what is the recommended way to enable KJ_DBG output on the sandstorm-http-bridge? do i need to repackage my app for that? (cannot find any --verbose handling)

12:33 <dwrensha> reisi: `make continuous` in one terminal and then `make update` in another

12:35 <dwrensha> to debug sandstorm-http-bridge, I usually insert a bunch of `KJ_LOG()` statements

12:36 <dwrensha> you do need to rerun `spk dev` or `spk pack` for changes to sandstorm-http-bridge to make it to your app

12:38 <reisi> dwrensha: oh, didn't realize that last one part, neither the building info but the last one is more significant :)

12:39 <reisi> i've been trying to debug why my modifications to sandstrom-http-bridge are not visible and the reason is i packaged my app with vagrant-spk (don't know how to do it yet with plain spk)

12:40 <dwrensha> are you building Sandstorm inside or outside of the vagrant VM?

12:41 <reisi> dwrensha: inside; i have had two vagrant boxes, one for compiling and running sandstorm, another one for packaging via vagrant-spk

12:44 <reisi> but next i'll figure out how to package with the spk i've just compiled and installed

12:46 <dwrensha> my usual method is to copy sandstorm-0-fast.tar.xz into the vagrant-spk vm and then do `sudo sandstorm update sandstorm-0-fast.tar.xz`

12:47 <reisi> oh yes of course

12:53 <reisi> nice, it'd seem my simple patch works :)

14:29 <asheesh> reisi: BTW (a) hooray that your patch works! and (b) if you're interested/able to write up a blog post or something like that on your own blog about what you learned about how to modify the Sandstorm shell, then that'd be amazing.

14:29 <asheesh> I can work on adding something to the main Sandstorm docs in the fullness of time, but I figure if you blog it yourself, then I'm not a roadblock for getting that in, and you don't have to worry as much about copying the docs.sandstorm.io writing style etc.

14:30 <asheesh> If you don't want to, that is fine too, but I thought I'd ask!

14:30 <asheesh> theSoenke: Hi there! So I noticed you're doing a thing that requires network access.

14:30 <asheesh> You will have to do some kind of capnproto stuff to get real outbound network Internet access.

14:31 <asheesh> Let me see what I can dig up in terms of details.

14:32 <asheesh> Some things to know about the code to give you network access to the outside world:

14:32 <asheesh> - Getting it working well is a priority within Sandstorm.

14:33 <asheesh> - We don't feel to that it's at the point het where lots of people can easily use it, so we haven't spent time trying to publicize it because we don't want to lead people into some experience that's surprisingly hard.

14:34 <asheesh> - We maintain the code actively and revise it periodically; https://github.com/sandstorm-io/sandstorm/blob/master/tests/apps/ip-networking.js is some automated tests that include some SPK links.

14:35 <asheesh> - You can use the Python test app to "Request IpNetwork", and you'll see the Sandstorm permission chooser (aka powerbox) UI. Note that only admins on the server have the ability to grant "IpNetwork" right now, which means it works for self-hosters but doesn't really work on Oasis unless you're Kenton.

14:38 <asheesh> - Once you click "Request IpNetwork" you'll see new app functionality that uses outbound raw Internet access. (In this case it's a HTTP fetch, but your app can do whatever.)

14:39 <asheesh> - You can see the Python source here: https://github.com/zarvox/sandstorm-test-python/blob/master/main.py

14:40 <asheesh> s/at the point het/at the point yet/

14:59 <theSoenke> asheesh: thanks a lot. i will take a look at it and try to implement it

15:46 <asheesh> theSoenke: You're welcome! Also do note that nodejs has capnproto bindings, and you can use that too; see https://github.com/kentonv/node-capnp

15:47 <asheesh> As you begin, I do personally recommend that you say hello on the sandstorm-dev Google Groups email list; letting people know what you're up to in a medium like email, where history is easier to access, is often a really good idea.

15:47 <asheesh> Not the slighest bit required, but just a random bit of advice.

15:48 <asheesh> AFK again for a while, alas!

15:52 <theSoenke> sure. will do that

16:41 <asheesh> And while I'm saying things here: Morning, all!

18:03 <asheesh> : D