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
<isd>
So I've got some mysql55 binaries seemingly peacefully co-existing with the new ones inside the grain. Now I just have to figure out how to actually do the cutover.
<isd>
ocdtrekkie: pushed a fix to the market, review when you can.
<isd>
Successfully upgrades the grain backup I was sent.
<JacobWeisz[m]>
I spy nix, lol
<JacobWeisz[m]>
Question: Since many pre-vagrant-spk 1.0 apps may use mysql 55, is this something that should be added to the stack? The uwsgi stack has MySQL too.
<JacobWeisz[m]>
There's a lot of conventions you used I think we should mostly just include. When I got my website working in Sandstorm I used your TTRSS scripts as an example.
<JacobWeisz[m]>
A lot of PHP apps assume you'll upload a database script or something ahead of time, I think all of your db-created logic might make sense to use in the stack itself.
kentonv has joined #sandstorm
<JacobWeisz[m]>
Ian, question, if I'm already running 5.7, what stops this new code from running?
<JacobWeisz[m]>
Oh, I see, you deleted that folder elsewhere already in the old version.
<JacobWeisz[m]>
That makes sense to me.
<JacobWeisz[m]>
Approved
<isd>
Glad you fiugred it all out while I was afk :P
<isd>
But yeah, probably a lot of that should be folded into the existing stack.
<JacobWeisz[m]>
So "go mod init" doesn't import anything from the gopath method, I have to find all the dependencies and add them myself?
<JacobWeisz[m]>
go mod tidy... hmmm
<isd>
It should just find them without you needing to do anything..
<JacobWeisz[m]>
Like with a fresh go.mod, I should just run vagrant-spk dev?
<isd>
Yeah.
<JacobWeisz[m]>
I guess I didn't try that.
_whitelogger has joined #sandstorm
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 240 seconds]
strugee has quit [Ping timeout: 264 seconds]
strugee has joined #sandstorm
_whitelogger has joined #sandstorm
ill_logic has joined #sandstorm
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 240 seconds]
frigginglorious has joined #sandstorm
frigginglorious has quit [Remote host closed the connection]
frigginglorious has joined #sandstorm
frigginglorious has quit [Remote host closed the connection]
frigginglorious1 has joined #sandstorm
frigginglorious1 has quit [Read error: Connection reset by peer]
frigginglorious has joined #sandstorm
<isd>
So, I'm investigating possible options for backup solutions for sandstorm, and I came across https://kopia.io
<isd>
I have open questions still about integration as far as a solution for backing up sandstorm & sandstorm grains, but it might be interesting to folks as-is: I might start using it to back up my machines to a davros grain, since it apparently supports webdav.
<isd>
(disclaimer: have not actually tried it yet)
frigginglorious1 has joined #sandstorm
frigginglorious has quit [Ping timeout: 256 seconds]
frigginglorious1 is now known as frigginglorious
griff_ has joined #sandstorm
frigginglorious has quit [Read error: Connection reset by peer]
frigginglorious has joined #sandstorm
frigginglorious has quit [Ping timeout: 246 seconds]
frigginglorious has joined #sandstorm
frigginglorious1 has joined #sandstorm
frigginglorious has quit [Ping timeout: 264 seconds]
frigginglorious1 is now known as frigginglorious
frigginglorious has quit [Read error: Connection reset by peer]
frigginglorious has joined #sandstorm
frigginglorious has quit [Ping timeout: 256 seconds]
<blowfist>
isd: automatically backup grains to a remote davros grain? Sounds great. Would it be from the command line?