kentonv changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev
prompt-laser has quit [Quit: Connection closed for inactivity]
ill_logic has joined #sandstorm
prompt-laser has joined #sandstorm
prompt-laser has quit [Quit: Connection closed for inactivity]
prompt-laser has joined #sandstorm
prompt-laser has quit [Quit: Connection closed for inactivity]
<isd>
Office hours in 1 hour.
<isd>
...we should find some way to automate updating of the wiki. It's surprisingly tedious and we seem to be slacking on it more and more.
<isd>
Ok, I updated it.
<isd>
ocdtrekkie: heads up, just submitted an update to yata.
<JacobWeisz[m]>
Woot
<isd>
I figured it was about time I got around to fixing that bug. Yata is about as close to "done" as software gets.
<kentonv>
ugh I keep forgetting about office hours. :(
<JacobWeisz[m]>
I know DokuWiki's first update in three years is around the corner too.
<JacobWeisz[m]>
I totally forgot about office hours today, I was actually at my PC that whole hour.
<JacobWeisz[m]>
WTB an Office Hours SandCal I can subscribe to.
<isd>
Ended up only being 15 min because it was just me and abliss
<isd>
(...again)
<abliss>
we have CalDav, I think you can subscribe there.
<isd>
(Actually, you could import the event into sandcal if you craft it elsewhere...)
<isd>
sandcal is in this weird state where it's replaced the thing I was using before, but is still incredibly janky.
<JacobWeisz[m]>
I mean, we have plenty of janky apps...
<JacobWeisz[m]>
Slap a beta label on it and ship it. ;)
<isd>
abliss: Do we have anything besides radicale that does caldav right now?
<isd>
ocdtrekkie: I think alpha is maybe the best I can begin to claim
<isd>
I can upload an spk somewhere though if you want to play with it...
<JacobWeisz[m]>
I would definitely play with it. But yeah, I mean, at the point where you're not losing data and you're not going to break upgrades... It's good to get more eyes on it.
<isd>
Storage format isn't changing much, I don't anticipate it will be hard to keep existing grains working.
<JacobWeisz[m]>
I filed my first jank report. ;)
<isd>
Thanks.
<JacobWeisz[m]>
Yata updated approved too
<isd>
cool
<JacobWeisz[m]>
I switched my shopping list grain over to it too.
<JacobWeisz[m]>
I really want to try migrating some old PHP sites of mine into Sandstorm, the scaffolding shared hosting gives you to work with is so nice though.
<JacobWeisz[m]>
I feel like shoving phpMyAdmin into a grain for management would be silly, but it's so handy.
<JacobWeisz[m]>
To move stuff into Sandstorm, my app's code has to be able to do all the stuff I'd just pop into the database editor for.
<JacobWeisz[m]>
I wonder... If we had a phpMyAdmin app, that of course, accessed it's own database, and I had a way to flip a grain to open with a different app... (which can be done at worst by manipulating metadata of a backup)... I could have the ability to service the grain's database within Sandstorm.
<isd>
You could maybe just map it to a different path within the grain?
<JacobWeisz[m]>
It just feels really heavy to pack that in with my website...
<isd>
Does it even impose any overhead besides making the spk bigger?
<isd>
Though more broadly it would be nice if it was easier to unbundle the notions of code and data in sandstorm.
<isd>
Another tack to experiment with would be to make powerbox requests for mysql connections. So supporting grains could allow other grains to request a connection to their mysql db.