<azirbel>
anyway, any tips on where to start debugging this would be much appreciated! `vagrant-spk dev` is a pretty slow command so it might take me a while.
<azirbel>
also, would love any/all tips on how to develop an ember application inside sandstorm without rebuilding it all the time.
<zarvox>
azirbel: eep. I wonder if you're hitting the VirtualBox shared folder kernel oops bug.
M-hrjet has joined #sandstorm
<azirbel>
shared folder problems sound likely
<zarvox>
try "vagrant-spk vm ssh" to get a shell on the VM, and then "dmesg" to see if there's a recent oops?
<azirbel>
I got it kinda-working via vagrant-spk dev, and then went back to development on my local system, and now tried again to run it inside sandstorm and got this problem
<azirbel>
dmesg spit out a bunch of stuff, but I have no idea what it is
<zarvox>
if you can pastebin it, I'll take a look at it
<azirbel>
I've finally reached the bleeding edge! how exciting!
<zarvox>
I've heard that some people observe that it is fixed when they "vagrant-spk vm destroy" and "vagrant-spk vm up" again. I suspect it's an issue with mismatched host/guest additions versions, or guest kernel version mismatch, or something
<zarvox>
VirtualBox's shared folder code has been a thorn in my side since 2013
<azirbel>
ok will try that
<zarvox>
as for having a better workflow with ember apps -- I think mnutt developed Davros with Ember, and had some techniques for making the iteration cycle faster.
<zarvox>
which appears to restart spk dev whenever changes are detected in your app
<azirbel>
oh yeah! thanks for reminding me, I saw that a long time ago and had forgotten where
<azirbel>
ember-cli-vagrant-spk looks perfect
todayman has quit [Remote host closed the connection]
TC01 has quit [Read error: Connection reset by peer]
<azirbel>
in theory, would you imagine people should be developing against a sandstorm-installed version of their app? Or develop against a locally run version, and then port to sandstorm after?
<azirbel>
Finally, you should realize that you don't need to do all your development through spk dev. If you spk pack and install your app, you can still edit the code in-place in the var/sandstorm/apps/<pkdId> directory where it was installed.
<azirbel>
...but don't fully understand it.
<zarvox>
Ahhh. That's more or less us admitting that the tracing filesystem performance combined with Rails' nonchalance for making excessive FS syscalls makes development super painful.
todayman has joined #sandstorm
TC01 has joined #sandstorm
<zarvox>
And offering a kinda-weird workaround to make it less of a problem.
<zarvox>
In an ideal world, I'd like to think that developing with vagrant-spk dev would be nice, and as apps want to integrate with more of Sandstorm's API surface/features (e.g. powerbox, user info, profile pictures, etc.), they'll have a better experience doing so with vagrant-spk dev.
<zarvox>
For apps which are not Sandstorm-first or which are primarily deployed outside of Sandstorm, it might make more sense for the authors to develop and test in those environments.
<azirbel>
ok cool, I'd think so too! I'm hoping to develop inside sandstorm now so I can see permissions working, because I have users with different roles
<zarvox>
I hope some day we can move away from VirtualBox and the problems it causes for users and towards something using the native hypervisors of each platform, but right now we don't have the manpower to invest in that kind of tooling infrastructure
<azirbel>
hey, great news! `vagrant-spk vm destroy && vagrant-spk vm up` worked, the app boots again now. Thanks zarvox!
<zarvox>
hooray! Sorry for the trouble, but glad to hear things are working again. :)
<zarvox>
that bug has caused seemingly random issues with Meteor apps for at least 7 months now
<azirbel>
my `vagrant-spk dev` is really slow, and one reason seems to be `npm install`. I bet it's reinstalling from scratch every time. Is there a better way?
eternaleye has joined #sandstorm
davidar has joined #sandstorm
<azirbel>
ah, I think ember-cli-vagrant-spk is probably that better way.
frigginglorious has quit [Ping timeout: 264 seconds]
jemc has joined #sandstorm
jadewang has quit [Remote host closed the connection]
jacksingleton has quit [Ping timeout: 264 seconds]
eternaleye has quit [Changing host]
eternaleye has joined #sandstorm
peterood has quit [Quit: Connection closed for inactivity]
jemc has quit [Ping timeout: 252 seconds]
frankier has joined #sandstorm
<azirbel>
actually, still confused. mnutt, if you happen to come by - where did your `npm install` go? It doesn't look like it's in `ember-cli-vagrant-spk`.
lukexj has quit [Ping timeout: 244 seconds]
lukexj has joined #sandstorm
Jan\ has joined #sandstorm
lukexj has quit [Quit: Leaving]
lukexj has joined #sandstorm
xobs has quit [Ping timeout: 246 seconds]
xobs has joined #sandstorm
decipherstatic has quit [Quit: Leaving]
azirbel has quit [Quit: Connection closed for inactivity]
tobald has joined #sandstorm
nwf_ has joined #sandstorm
nwf has quit [Ping timeout: 244 seconds]
lukexj has quit [Ping timeout: 244 seconds]
nwf_ is now known as nwf
lukexj has joined #sandstorm
booseye_eshgh45 has joined #sandstorm
booseye_eshgh45 has quit []
frigginglorious has joined #sandstorm
afuentes has joined #sandstorm
tobald has quit [Quit: Ex-Chat]
<simonv3>
is there an RSS feed in the work that works responsively on smaller screens? TTR doesn’t do that very well :(
<dwrensha>
simonv3: tinytinyrss has apps for mobile that work with sandstorm
<simonv3>
dwrensha: oooh, really?
<simonv3>
I’ll explore
<dwrensha>
getting it set up is a bit tricky
<dwrensha>
you need need to click the webkey button in the sandstorm topbar to generate a token
<dwrensha>
and then paste various pieces of that webkey/token into various places in the ttrss config area
<dwrensha>
I have it working on android
<dwrensha>
I'm not sure if ios works
<simonv3>
android is what I have, so I’ll have a look
<frigginglorious>
simonv3: they have a 1 month trial app, and then you can buy it for $4 or $1 or something. i had downloaded it, but i forgot to try it.
<dwrensha>
really? I've had if for more than a month, and I don't remember paying for anything
<frigginglorious>
but i would like to hack away at TTRSS some day.
<simonv3>
It says “Trial version. Buy if you like”, guess it’s optional?
<simonv3>
dwrensha: would I just paste the webkey into the connection URL?
<dwrensha>
the fragment part of the webkey is the token
<dwrensha>
that's your password
<dwrensha>
(fragment = part after the "#")
<dwrensha>
the part before the "#" is the connection URL
<dwrensha>
and any username should work
<dwrensha>
and I think there's one more confusing thing that I got wrong the first time....
<simonv3>
ah
<dwrensha>
hm... yeah it's confusing becuase there is "Tiny Tiny Rss Account" username/password
<dwrensha>
and also HTTP auth username and password
<dwrensha>
The instructions I just gave you apply to the HTTP auth stuff
<dwrensha>
maybe you just leave the TTRSS account stuff blank?
xet7 has joined #sandstorm
<simonv3>
hmm, yeah, I can’t get it right. I’m putting the fragment (stuff after the ‘#’) in the HTTP-Auth password field, and just “simon” in the username (I’ve tried blank, and a couple of other things) and the URL minus the fragment in the Connection URL. variously trying with ttrss account stuff blank and filled in. I just see the “server returned
<simonv3>
status 401 unauthorized error” with link to “preferences” to set it up.