16:49 <mrdomino> oh shit guys, sandstorm offline mode

16:49 <mrdomino> i have a wiki i'm working on

16:49 <mrdomino> i just realized i could start up my own sandstorm instance, import the backup, and work on it there

16:49 <mrdomino> this is amazing

17:11 <zarvox> mrdomino: note that you can't restore the modified wiki to the original URL, but if you've already indirected that (or don't mind mucking with the grain storage directly), then: nice, clever!

18:58 <mrdomino> zarvox: ah yes, good point. hmm. is it a bug?

19:12 <zarvox> mrdomino: I don't think it's a bug. I could be convinced that it's a potentially-valid feature request, but probably one that would make more UX sense in the context of a more well-thought-out backup/restore/revision history/etc. workflow

19:16 <zarvox> for instance, people might be afraid about app upgrades potentially causing regressions in grains (or just changing the way the app behaves in a way they dislike), and they'd like the ability to snapshot the grain's state before the upgrade has a chance to change it in some backwards-incompatible way

19:16 <mrdomino> sure

19:16 <zarvox> or it might be nice to be able to save e.g. daily/weekly/etc. backups

19:16 <mrdomino> fwiw i was using bug in the "a feature you don't have yet is a bug" sense

19:17 <mrdomino> yeah that'd be pretty awesome

19:17 <zarvox> and then that "restore to that old URL" becomes "make an additional revision in this history"

19:17 <zarvox> "from an external source"

19:20 <zarvox> That said, I suspect we won't be working on that set of features for a while

19:21 <zarvox> Hence the alternative suggestion of "copy your new data into /opt/sandstorm/var/sandstorm/grains/$GRAINID/sandbox" (which is /var as seen from within the grain) :)

21:20 <frew> I'm just trying out sandstorm, and it seems pretty awesome

21:20 <frew> I'm trying out Tiny Tiny RSS in sandstorm first since I run that myself on my own host

21:20 <frew> a couple questions

21:21 <frew> 1) does anyone know if there would be a way I could seed the database of a fresh grain or do I need to do an export/import?

21:21 <frew> 2) I see that there's the API option, but will that work with, for example, the TTRSS mobile app which doesn't know about the extra Authorization header?

21:22 <frew> I would also LOVE to make a weechat grain, but I'd have to basically have weechat with an SSH endpoint. It seems like this is very browser centric. Can other ports be exposed?

21:26 <frew> looks like the TTRSS app needs to be added to the whitelist.

21:29 <frew> ugh, and it's UA is Dalvik/2.1.0 (Linux; U; Android 6.0.1; A0001 Build/MMB29X)

22:22 <frigginglorious> anyone know what the BIND_IP field is in sandstorm.conf?

22:22 <frigginglorious> right now its just set to 0.0.0.0. That should be global, right?