ocdtrekkie has quit [Read error: Connection reset by peer]
ocdtrekkie has joined #sandstorm
harish_ has quit [Ping timeout: 256 seconds]
jemc has quit [Ping timeout: 268 seconds]
digitalcircuit is now known as Guest23330
digitalcircuit has joined #sandstorm
Guest23330 has quit [Read error: Connection reset by peer]
harish_ has joined #sandstorm
hsrai has quit [Ping timeout: 265 seconds]
hsrai has joined #sandstorm
ocdtrekkie_ has joined #sandstorm
ocdtrekkie has quit [Ping timeout: 264 seconds]
isd has joined #sandstorm
xet7 has joined #sandstorm
xet7 has quit [Ping timeout: 240 seconds]
xet7 has joined #sandstorm
isd has quit [Quit: Leaving.]
harish_ has quit [Ping timeout: 265 seconds]
harish_ has joined #sandstorm
harish_ has quit [Ping timeout: 256 seconds]
harish_ has joined #sandstorm
b00tcat has joined #sandstorm
<b00tcat>
hey all - is there any way to programmatically back up a sandstorm grain w/o having full access to the server? i.e. if I'm using sandstorm.io
<TimMc>
Oh, like on Oasis?
<TimMc>
b00tcat: Just from a very quick inspection at the console, I suspect the UI sends a websocket command to request a backup. The backup then appears to be a one-time download link like https://yourhost/downloadBackup/NobTIriTRFy5e5463
<b00tcat>
TimMc: I guess getting the necessary cookies to be able to talk to the websocket & stuff is not gonna be trivial
<TimMc>
Cookie might not be so bad. That token you get from logging in by email is pretty long-lived.
<TimMc>
websocket sounds annoying
<b00tcat>
it is :D it'd be nice to have a client-side command line interface to interact with sandstorm but that's still an open request sadly
<b00tcat>
I'll figure something out
<b00tcat>
thanks anyway!
<TimMc>
b00tcat: If you stick around in the channel one of the people more familiar with the code *might* have better news.
<ocdtr_web>
b00tcat: I also would very much like an easy way to backup my Oasis grains. I noted on the GitHub issue relevant to it that an IRC user also noted interest. :)