04:45 <DanC> hmm... I just re-discovered https://www.pythonanywhere.com/ ... I think a lot of times I'm in the mood to use something like that in sandstorm.

04:45 <DanC> sort of a remote development thingy

04:46 <DanC> kinda like adding javascript code to google spreadsheets and stuff

04:47 <DanC> Their tabs are: Consoles, Files, Web, Schedule, Databases. The Databases tab asks me to make up a mysql password to start a server. Boring; why don't they make up a password for me? oh well.

04:47 <DanC> sandstorm has a Files thingy

04:52 <DanC> "Your Scheduled task is a script that will run every day at a time of your choosing — you can use it to do stuff like scraping websites, or checking that your server is running." wow... that's a lot of potential for abuse

19:21 <BlueNinja> hey ppl :)

19:22 <BlueNinja> b

19:23 <BlueNinja> Ive been wondering whats new with sandstorm / grains development.. Every week I look at whats new and updated, but I dont see a lot of movement.

19:30 <isd> Things have been much slower since sandstorm-the-startup shut down. Happens when you go from several full-time employees to a volunteer-only project. I think kentonv is working on this: https://sandstorm.io/news/2017-05-08-refactoring-identities

19:31 <isd> I *hope* more folks start to get involved in core. I've seen a patch or to related to testing.

19:32 <isd> I've done some really trivial doc/cleanup stuff, but as much as I'd like to make improvements to core, I don't think I'm going to be able to get myself to do a bunch of hacking on a codebase that's mostly Javscript & C++ -- don't want to start a language flamewar, suffice it to say I'm really not a fan.

19:33 <isd> I've been playing with protocols to share filesystems between grains: https://github.com/zenhack/sandstorm-filesystem

19:33 <BlueNinja> nice, well I really believe in sandstorm

19:33 <isd> Which hopefully will have some broader applicability. I'll probably post an announcement/call for feedback in the next week or so, but I want to finish up the demo app first.

19:33 <BlueNinja> and I want to see more developers hop in and make grains.

19:33 <BlueNinja> I think the portability and security and ease to them is unmatched

19:33 <BlueNinja> so I hate to see this fizzle out

19:34 <isd> yeah, same.

19:35 <isd> I do think long term we need more people outside the original team to start hacking on core for the project to stay healthy.

19:36 <isd> I'm probably going to end up focusing on dev tools and apps myself.

19:36 <isd> Though if I can find the time somewhere I'd like to take a whack at the distro project.

19:37 <isd> and I can think of a handful of other contributions I'd like to make that don't involve too much interaction with the bits I have an aversion to

19:46 <BlueNinja> well.. any way I can help. Im no longer a developer but if there is a great YT vid or something describing it, I can see about showing a lot of ppl

19:49 <isd> BlueNinja: https://sandstorm.io/community

19:49 <isd> Some food for thought; a good number of non-dev things on that list.

19:51 <BlueNinja> nice, Ill take a looksy at it

23:17 <limbo_> Is there a version of sandstorm I can install on a server that doesn't need to phone home, and won't mess with my already installed services. (mainly webserver)

23:19 <limbo_> also, is running x86_64 nessisary?

23:20 <sknebel> x86_x64 is necessary, yes. I'm not sure if you can turn off the update checker, but sandcats is optional and sandstorm doesn't mess with other services (well, if you tell it to use port 80 then it of course will try to use that, so just don't do that ;))

23:25 <isd> limbo_, sknebel: I'm pretty certain you can turn off the update checker. I'd have to dig a bit to figure out how.

23:26 <isd> But yeah, do that and don't use sandcats, and it won't talk to any of the community infrastructure.

23:45 <limbo_> swell. Any documentation on migrating an nginx install that I use for some static content?

23:46 <limbo_> sknebel: Any idea what depends on x86_64? Is it just binary updates, or is there something that hasn't been ported to other systems?

23:49 <sknebel> limbo_: I think it's primarily that the app packages are provided by the packagers as binaries, and there is no system to have them for multiple architectures

23:54 <isd> There are also probably a few bits that would need porting. I'm not sure how much libseccomp abstracts away, but bpf filters are architecture specific, so that bit of the supervisor might need to be ported.

23:54 <isd> But yeah, the main thing is app portability

23:54 <isd> There's a relevant issue open, let me find it

23:55 <isd> here: https://github.com/sandstorm-io/sandstorm/issues/2083

23:57 <limbo_> dang. Know of anyhting like sandstorm that supports ARM?

23:58 <limbo_> Isolation is less important to me than seperation.

23:58 <limbo_> s/seperation/easy install