gopar has quit [Remote host closed the connection]
losvedir has joined #sandstorm
home has quit [Ping timeout: 240 seconds]
losvedir has quit [Quit: losvedir]
losvedir has joined #sandstorm
losvedir has quit [Client Quit]
todayman has quit [Ping timeout: 255 seconds]
todayman has joined #sandstorm
losvedir has joined #sandstorm
losvedir has quit [Ping timeout: 240 seconds]
larjona has joined #sandstorm
<ckocagil>
sup channel
mort___ has joined #sandstorm
larjona has quit [Ping timeout: 272 seconds]
jadewang has joined #sandstorm
rustyrazorblade has joined #sandstorm
mnutt_ has joined #sandstorm
xet7_ has joined #sandstorm
<rustyrazorblade>
hi
sunu has quit [Quit: No Ping reply in 180 seconds.]
sunu has joined #sandstorm
jadewang has quit [Remote host closed the connection]
sunu has quit [Client Quit]
sunu has joined #sandstorm
sunu has quit [Quit: No Ping reply in 180 seconds.]
sunu has joined #sandstorm
gopar has joined #sandstorm
sunu has quit [Client Quit]
Guest58485 has joined #sandstorm
<zarvox>
ckocagil: I got your gogs port up and running!
<ckocagil>
zarvox: cool!
<zarvox>
Do you think it'll make sense to add the .sandstorm stuff to the main gogs repo, and build from the go sources?
<zarvox>
We'll probably have to adjust the accessing-the-repository instructions for Sandstorm, since you can't (yet) connect over SSH, and HTTPS requires using the API host and a randomly-generated auth token
<zarvox>
You can take a look at how that's done in the gitweb and gitlab ports, but we should probably write some proper documentation for what we call "offer templates"
<ckocagil>
zarvox: yeah I'll have to fork the main repo anyway
<ckocagil>
zarvox: I got the offer templates working, but gogs's access control has to be modified
<zarvox>
oh wow, awesome!
<ckocagil>
zarvox: do you know if the app gets X-Sandstorm-* headers when a request comes from an app?
<ckocagil>
I'm talking about non browser HTTP requests with a key
<zarvox>
Requests passed on from the api endpoint include the X-Sandstorm-* headers, yes
<ckocagil>
okay, nice
<ckocagil>
zarvox: I'm not sure if there's any benefit to keeping the Gogs modifications on a repo separate from .sandstorm
<zarvox>
I usually forget what all gets passed on, and wind up doing something like "sudo strace -ff -s 1024 -p $(pidof sandstorm-http-bridge)" in the VM (vagrant-spk ssh to get a shell) to see exactly what's getting passed on from sandstorm-http-bridge to the app
<ckocagil>
zarvox: nice tip!
<zarvox>
ckocagil: I think the ideal situation would be that someday, upstream Gogs carries your changes, detects if it's running under Sandstorm, and switches to your modified codepaths for access controls and offer templates and so on
<ckocagil>
understood. separate repo then.
<zarvox>
for now, I'm perfectly happy with keeping all the "make-it-work-under-sandstorm" changes on the same branch on a single repo for everything
<zarvox>
sorry, I don't think I was clear - I think you should keep your .sandstorm additions in the same repo as the gogs changes, and that repo should be based on upstream gogs :)
jadewang has joined #sandstorm
<augustl>
anyone got "wave" to work? I always get "A turbulence detected!"
<zarvox>
augustl: Hmmm. That could be wave crashing or running out of memory. Where are you running this?
<ckocagil>
Did anyone try porting Seafile? It seems(?) to have an http protocol
<augustl>
zarvox: self hosting
<augustl>
about one meter away from where I'm sitting now ;)
<zarvox>
augustl: how much RAM does that machine have?
<augustl>
zarvox: 10gb
<zarvox>
okay, probably not that then :P
<zarvox>
ckocagil: I don't think anyone's tried yet! That would pretty fantastic.
<augustl>
hmm, someone should totally package up discourse for sandstorm
<zarvox>
augustl: that'd be interesting! It might take some thought to figure out the right granularity for grains - is a grain a whole forum, a board, a thread, or something in-between?
<augustl>
weird, where would I find log files for the wave grain on my own standstorm instance?
<zarvox>
/opt/sandstorm/var/sandstorm/grains/<grainId matching the thing in that grain's URL>/
<ckocagil>
you can try downloading the state and checking there
<zarvox>
under that folder, sandbox is what the grain sees as /var
<zarvox>
huh, I just got the "Turbulence detected!" message
<zarvox>
Could be the websocket breaking? Unclear.
<augustl>
ah, I'm using apache 2.2 which doesn't have websocket support
<zarvox>
Ahhh, that might cause issues, then. The Sandstorm shell probably falls back to using long-polling/whatever Meteor does by default, but Wave may not degrade as gracefully.
mort___ has quit [Quit: Leaving.]
rustyrazorblade has quit [Quit: rustyrazorblade]
<XgF>
augustl: discourse requires PostgreSQL AND Redis. This does not seem appropriate for Sandstorm :P
<augustl>
hmm, how come? My server is beefy :)
<XgF>
augustl: Because each grain would have ridiculous resource demands
<augustl>
seems like discourse isn't a good fit for the grain model
<zarvox>
Discourse is indeed pretty heavyweight.
<zarvox>
I don't see anything wrong in principle with grains having an e.g. PostgreSQL and Redis instance though, if they're configured to be reasonably lightweight.
larjona has joined #sandstorm
<zarvox>
Plenty of PHP apps depend on MySQL, and while it's maybe sad that each grain takes ~30MB minimum for MySQL, that's still way better than lots of people not being able to run the software at all :)
larjona has quit [Ping timeout: 246 seconds]
<zarvox>
Maybe someone should look into seeing how lightweight Postgres can be made!
<XgF>
zarvox: Though redis takes linear memory with linear data
<augustl>
would be neat if sandstorm allowed multiple grains to share a postgres/redis setup :)
<zarvox>
that would break the security boundaries, and would probably require more user work than "click button, receive instance"
<zarvox>
But maybe it'd be a reasonable compromise for things that you want to run at scale for public-facing services? Hard to say. Probably a ways out into the future.
<ckocagil>
Aha, I got the same error as a few days ago
<ckocagil>
Machine already provisioned. Run `vagrant provision` or use the `--provision`
mort___ has joined #sandstorm
simonv3 has joined #sandstorm
patrickod has quit [Ping timeout: 240 seconds]
mort___ has quit [Quit: Leaving.]
larjona has joined #sandstorm
<paulproteus>
ckocagil: Hi!
<ckocagil>
hey paulproteus
<paulproteus>
"Machine already provisioned" is just a note, not an error.
<paulproteus>
Perhaps we should silence that since it's meaninglesss.
<ckocagil>
paulproteus: Whenever that line prints, sandstorm doesn't run in the vm
<ckocagil>
in contrast to "Running provisioner: shell...
<ckocagil>
"
<paulproteus>
Oh, whoa, huh ckocagil
<paulproteus>
When you do
<paulproteus>
vagrant-spk ssh
<paulproteus>
and you do
<paulproteus>
sudo less /opt/sandstorm/var/log/sandstorm.log
<paulproteus>
Do you see any useful (?) information in the log file?
<ckocagil>
paulproteus: nope, seems normal
<paulproteus>
sudo service sandstorm status
<paulproteus>
also might possibly be useful.
<ckocagil>
sadly I power cycled the machine and it works now
<ckocagil>
paulproteus: sandstorm/util.c++:800: failed: expected exitCode == 0; child process failed; name = ; exitCode = 100
<paulproteus>
Ouch
<paulproteus>
Lemme read the log
<paulproteus>
Huh.
<paulproteus>
Are there any other lines in the log? That's so interesting, and it really shouldn't happen, so I'd like to debug it further if possible.
<ckocagil>
let me see
<paulproteus>
Sure is sad that name is the empty string.
<paulproteus>
OK this old lock file thing looks relevant!
<ckocagil>
heh, it makes sense that util.c++:800 is an assertion for the child process exit status
<paulproteus>
I should head out for now but I can try to debug this further on Monday or so, if that works for you. For now, I guess, reboot, but hopefully I can reproduce this and fix it.
<paulproteus>
reboot the VM, naturally.
<ckocagil>
paulproteus: but I want my money back...
<paulproteus>
If you can file a bug with this info, that'd be great.
<ckocagil>
okay, filing a bug
<paulproteus>
If not, I can file a bug e.g. tomorrow. github.com/sandstorm-io/sandstorm/issues IMHO
<paulproteus>
Thanks! Going AFK for a bit.
<ckocagil>
have a good day
yuvipanda has quit []
larjona has quit [Quit: Konversation terminated!]
simonv3 has quit [Quit: Connection closed for inactivity]