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
xet7 has quit [Read error: Connection reset by peer]
xet7 has joined #sandstorm
frigginglorious1 has joined #sandstorm
frigginglorious has quit [Ping timeout: 265 seconds]
frigginglorious1 is now known as frigginglorious
* isd searches for hcalendar
<isd> Good to know about. Writing a decent sandstorm calendar app is vaguely on my todo list; may try to incorporate.
_whitelogger has joined #sandstorm
frigginglorious has quit [Read error: Connection reset by peer]
_whitelogger has joined #sandstorm
wings has quit [Ping timeout: 260 seconds]
wings has joined #sandstorm
wings has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
frigginglorious has quit [Ping timeout: 240 seconds]
wings has joined #sandstorm
ocdtrekkie has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
frigginglorious has joined #sandstorm
_whitelogger has joined #sandstorm
abliss has joined #sandstorm
<abliss> I'm trying vagrant-spk for the first time, and getting a 404 because i get redirected to https://app.terraform.io/debian/boxes/jessie64/versions/8.2.1/providers/virtualbox.box which is gone. any tips?
<abliss> seems to work if i replace `sandstorm/debian-jessie64` with `debian/jessie64` in the Vagrantfile. The former claims to be a "bit-for-bit" copy of the latter... any reason not to do this?
ogres has joined #sandstorm
ocdtr_web has joined #sandstorm
<ocdtr_web> abliss: At bare minimum you need contrib-jessie64 or contrib-stretch64.
<ocdtr_web> But if you are going to update an old app, you might want to go ahead and update to stretch.
<ocdtr_web> If you vagrant-spk init in a new directory like you're creating a new app, you'll get a more modern Vagrantfile and global-setup.sh
<abliss> thanks. what does updating to stretch look like? is sandstorm/debian-stretch64 a thing?
<ocdtr_web> No, the Sandstorm-specific box is gone.
<ocdtr_web> It just had some stuff vagrant-spk needs to work which is in contrib-
<abliss> so you're saying debian/jessie64 won't work? how do i add contrib- to my vagrant box?
<ocdtr_web> debian/contrib-jessie64 should work.
<abliss> got it, thanks
<ocdtr_web> vagrant-spk was pretty badly bitrotted. I am kinda of the opinion a good way to update apps is to vagrant-spk setupvm $stack, vagrant-spk vm up, vagrant-spk init, etc. in a new folder, and then overwrite a lot of the app's existing .sandstorm folder.
<ocdtr_web> Vagrantfile and global-setup.sh shouldn't require any modification to overwrite an existing app.
<ocdtr_web> It's mostly the build.sh, launcher.sh, and setup.sh that's likely to include app-specific things.
<abliss> how do i figure out $stack ? is it in the old Vagrantfile somewhere?
<ocdtr_web> Your app has a /.sandstorm/stack file which specifies the stack it used.
<ocdtr_web> If it's GitWeb, it's diy.
<ocdtr_web> And then you probably don't need to modify build.sh, launcher.sh, or setup.sh at all.
<abliss> yep, thanks, will give it a shot
<ocdtr_web> So yeah, get the latest Vagrantfile and global-setup.sh from following the instructions to make a new vagrant-spk app, and paste them in there, because there's probably half a dozen bugs we fixed from whatever was in the GitWeb folder.
<ocdtr_web> vagrant-spk creates those files on app creation, and never really had a good story for updating them as vagrant-spk is updated. I think that's something I'd like to tackle at some point.
<ocdtr_web> Possibly expressing in those two files especially not to modify them, and having a vagrant-spk command that overwrites them.
<ocdtr_web> On my todo list, in case you are curious: Merging the open vagrant-spk PR and then calling the following version vagrant-spk 1.0.
<ocdtr_web> Because the PR fixes the last stacks that were still broken from the jessie days.
<abliss> why does vagrant-spk default to listening on 6080, the same port a real sandstorm install listens on? I only have one x86_64 machine so I have to use it for both making packages and serving live traffic. why not make vagrant-spk default to 6081 so I don't have to override it everywhere?
<isd> abliss: I can't think of a good reason, my guess is it was just oversight. Want to submit a PR?
<ocdtr_web> abliss: I think 6081 is a default mongo port.
<ocdtr_web> for Sandstorm.
<ocdtr_web> So maybe not that one. :)
<ocdtr_web> I use a different dev machine but since I do spk dev and vagrant-spk dev sometimes I've definitely done sandstorm stop solely so I can vagrant-spk vm up.
abliss has quit [Ping timeout: 258 seconds]
<ocdtr_web> I would go for 6090. It doesn't appear in IANA's port list at all.
ogres has quit [Quit: Connection closed for inactivity]
frigginglorious1 has joined #sandstorm
frigginglorious has quit [Ping timeout: 260 seconds]
frigginglorious1 is now known as frigginglorious
pie_ has joined #sandstorm
pie_[bnc] has quit [Quit: No Ping reply in 180 seconds.]
pie_ has quit [Quit: pie_]
<ocdtr_web> Gosh darn it.
<ocdtr_web> abliss got me on a roll. vagrant-spk 1.0 is gonna have some changes.
ocdtr_web has quit [Remote host closed the connection]
nicoo has quit [Remote host closed the connection]
nicoo has joined #sandstorm