<crab>
well, i'm slowly working my way up to developing some apps for sandstorm.
<crab>
but the slowness is a definite drawback.
PrivateReese has quit [Ping timeout: 248 seconds]
PrivateReese has joined #sandstorm
harish has quit [Ping timeout: 240 seconds]
Lionel_Debroux_ has quit [Ping timeout: 240 seconds]
ogres has quit [Quit: Connection closed for inactivity]
<ocdtrekkie>
crab: Someone a lot smarter than me is going to have to figure out why that's occurring.
<ocdtrekkie>
georgeowell: I think updating a lot of the apps are probably low-hanging fruit because most of the work to make them work in Sandstorm is already done. I was discussing Telescope with someone last week: https://github.com/jparyani/Telescope/issues/10
<ocdtrekkie>
Meteor ports are pretty easy, I could probably do the new version if I had time (but I don't).
<crab>
do you perhaps have time to talk someone else through it?
<ocdtrekkie>
Very possibly. I worked with xet7 on setting up Wekan packaging, and that's meteor-spk based as well.
<ocdtrekkie>
I have pretty reasonable leeway on communicating with folks throughout the day, but from work and other places I end up I rarely have time to sit at home, spin up the Linux VM and :do:.
<crab>
well, i want to dedicate a few cycles towards sandstorm, but in terms of updating packages, i have absolutely no idea where to start. i guess i should read the vagrant-spk docs first and get it set up?
<ocdtrekkie>
The docs give a pretty good idea how to get started. vagrant-spk's tutorial is decent. Though I am generally used to using the regular spk tool or meteor-spk. (I do not believe vagrant-spk will currently work for Meteor apps.)
<crab>
oh.
<ocdtrekkie>
Basically, spk is the Sandstorm packaging tool, and then meteor-spk is a tool which handles Meteor dependencies so you can port Meteor apps easily, and vagrant-spk does a few things, like setting up development in a VM so you can package apps from OS X or Windows machines, and it automates setup of a few different platforms.
<ocdtrekkie>
In most cases, the 'easiest' way to update an app is probably going to be to continue using whatever way it was set up to begin with.
<crab>
and how do i find out what that is?
<ocdtrekkie>
Pretty much any app with a .sandstorm folder is vagrant-spk. Anything with a .meteor folder (without a .sandstorm folder) is meteor-spk. And everything else is just spk.
<xet7>
crab: Things missing from that page: using command to build spk package, signing package for Sandstorm. I will add those sometime.
<xet7>
After I get Wekan spk signed for Sandstorm etc
<xet7>
I do have instructions for that from ocdtrekkie but I have not done all steps yet
tobald has quit [Quit: Ex-Chat]
harish has joined #sandstorm
harish has quit [Ping timeout: 240 seconds]
frigginglorious has quit [Ping timeout: 248 seconds]
dcb has quit [Ping timeout: 264 seconds]
dcb has joined #sandstorm
georgeowell has quit [Quit: Leaving this Club]
xet7 has quit [Ping timeout: 240 seconds]
georgeowell has joined #sandstorm
tobald has joined #sandstorm
ocdtr_web has joined #sandstorm
<ocdtr_web>
crab: Note that a bunch of that was mitigating specifically an issue with Ubuntu's kernel. meteor-spk should more or less "just work" with other flavors of Linux.
<ocdtr_web>
I actually can't click GitHub links at the moment because GitHub is failing to succeed at TLS handshakes today.