<ocdtrekkie>
I'd be tempted to find out if I can use vagrant-spk's PHP specific stuff without the VM and such and make a smaller tool.
<ocdtrekkie>
But I haven't looked that closely yet.
<paulproteus>
The main difficulty with that is that we don't have a clean way (yet) of declaratively specifying which subsets of the system's PHP stuff an app needs.
<paulproteus>
We arguably could have just one VM that contains support for _all_ the Vagrant-SPK supported platforms.
<zarvox>
paulproteus: "just" install everything from main!
<paulproteus>
Or use buildpacks
<paulproteus>
Plus pre-generated file lists
<ocdtrekkie>
paulproteus: isn't that why Sandstorm watches what stuff you use?
<paulproteus>
Yeah, but that doesn't help if package1 needs file1 to have contents xyz but package2 needs file1 to have contents abc.
<XgF>
(If you're not installing stuff properly, just add the dir to PATH)
<zarvox>
XgF: for you, that's export PATH="$PWD:$PATH"
<zarvox>
;)
<zarvox>
but editing a user's .bashrc or whatever shell durably is super sketchy
<XgF>
I probably wouldn't want it permanently on my path anyway, unless I'd installed it
<XgF>
I don't dump all of my cross compilers on my path permanently either
<zarvox>
and if you just set PATH, then you might be confused if you opened a new shell and couldn't use it
<zarvox>
XgF: I think people like you and I will see that line, and go "oh, I know what this is doing, I'll set PATH instead"
<zarvox>
and the people who don't know what it means will be better served by the line as-is
<XgF>
One would expect users to understand how their shell works -.-
<XgF>
ocdtrekkie: I don't really see how useful something like vagrant-spk would be with Go, I mean, Go apps are statically linked...
<zarvox>
I suppose Go has a better cross-compilation story than most toolchains :P
<zarvox>
spk is still Linux-only, so if you're on OSX or Windows, you'd still need a VM for that, at present
<XgF>
zarvox: SPK is always going to be Linux-only by nature
<XgF>
At least in that the biggest part of what it does involves talking to a Sandstorm supervisor and dealing in Linux binaries
<zarvox>
Yeah. I could see a world where spk init, pack, and unpack were things that you could do on e.g. OSX or Windows. But more broadly, you're right.
<zarvox>
Still, I think a vagrant-spk stack for go that installs the go toolchain wouldn't be entirely useless :)
<XgF>
Yeah. I may dislike Go, but I don't dislike apps written in Go because they're generally still pretty lightweight, speedy and easy to deploy (most of them are statically linked binaries, trivial!)
natea has quit [Quit: natea]
natea has joined #sandstorm
<ocdtrekkie>
XgF: Just setting it up for me mostly.
<ocdtrekkie>
:P
<ocdtrekkie>
I tried to run one today, and I couldn't get it working at all.
sfbae has quit [Ping timeout: 244 seconds]
sfbae has joined #sandstorm
sfbae has quit [Ping timeout: 276 seconds]
natea has quit [Quit: natea]
natea has joined #sandstorm
sfbae has joined #sandstorm
natea has quit [Quit: natea]
<paulproteus>
Yeah, I do the ln thing because I don't trust that I have the ability to add things to people's paths.
dwrensha has quit [Ping timeout: 245 seconds]
sfbae has quit [Quit: a]
natea has joined #sandstorm
bb010g has joined #sandstorm
natea has quit [Quit: natea]
joshbuddy has quit [Quit: joshbuddy]
gopar has quit [Quit: Leaving]
joshbuddy has joined #sandstorm
joshbuddy has quit [Client Quit]
joshbuddy has joined #sandstorm
joshbuddy has quit [Client Quit]
dwrensha has joined #sandstorm
jadewang has quit [Remote host closed the connection]
decipherstatic has quit [Quit: No Ping reply in 180 seconds.]
[d__d] has quit [Remote host closed the connection]
[d__d] has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 240 seconds]
erikoeurch has quit [Quit: Leaving]
natea has joined #sandstorm
natea has quit [Quit: natea]
jadewang has joined #sandstorm
amyers has joined #sandstorm
jadewang has quit [Ping timeout: 255 seconds]
natea has joined #sandstorm
natea has quit [Quit: natea]
natea has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 240 seconds]
natea has quit [Quit: natea]
natea has joined #sandstorm
natea has quit [Quit: natea]
natea has joined #sandstorm
natea has quit [Client Quit]
ragesoss_ has joined #sandstorm
ragesoss has quit [Ping timeout: 272 seconds]
dwrensha has joined #sandstorm
jadewang has joined #sandstorm
natea has joined #sandstorm
jadewang has quit [Ping timeout: 265 seconds]
jadewang has joined #sandstorm
natea has quit [Quit: natea]
jadewang has quit [Ping timeout: 276 seconds]
ArcTanSusan has joined #sandstorm
ArcTanSusan has quit [Quit: ArcTanSusan]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 265 seconds]
jeffmendoza has quit [Remote host closed the connection]
Guest29143 has quit [*.net *.split]
preilly has joined #sandstorm
preilly is now known as Guest41327
dwrensha has quit [Ping timeout: 264 seconds]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 264 seconds]
joshbuddy has joined #sandstorm
dwrensha has joined #sandstorm
jadewang has joined #sandstorm
bb010g has quit [Quit: Connection closed for inactivity]
natea has joined #sandstorm
yeehi has joined #sandstorm
<yeehi>
Well done to the developers of Sandstorm! It looks lovely and the apps available on the demo work right out of the box.
<yeehi>
terrific!
<kentonv>
thanks!
<paulproteus>
: D
<yeehi>
What are the main aspects of Sandstorm that are being developed at the moment, kentonv?
<yeehi>
paulproteus recommended it, and I can see why.
<kentonv>
oh boy, lots of things
<paulproteus>
(-: Nice to see you here!
<yeehi>
Is there a roadmap?
<kentonv>
there's some stuff in the readme, but it's not really complete
<yeehi>
The big selling point for me was that Sandstorm made something as complex as setting up MediaGoblin into One Click! :)
<yeehi>
I checked the other stuff available there and it works very well
<kentonv>
we are working on making it easy to connect apps to each other ("powerbox"), making sharing easier, improving the UI, etc.
<kentonv>
sorry we're actually about to start a meeting here, but we'll be back a little later!
<yeehi>
kentonv, paulproteus, why would a webhosting service adopt Sandbox?
<yeehi>
OK, later, kentonv
yeehi has quit [Ping timeout: 256 seconds]
yeehi has joined #sandstorm
<ocdtrekkie>
Is there any chance of Diaspora working on Sandstorm soonish?
<ocdtrekkie>
Google+ has become unmanageable.
<kentonv>
ocdtrekkie: probably not "soonish". :( We struggled somewhat to fit their federation model into ours and decided that we need to build out our features more before it will work well.
<ocdtrekkie>
Google now blocks me and my friend from communicating because of a third party.
<kentonv>
?
<ocdtrekkie>
When my friend shares a public post, they should not have to be aware of whether or not the person they're sharing from has me blocked.
<ocdtrekkie>
My friend Jordan is sharing public posts, on public matters, but even if he tags me directly I cannot see them.
<kentonv>
everyone has a different opinion on what "block" should mean... but I agree, that seems silly
amyers has quit [Ping timeout: 252 seconds]
<ocdtrekkie>
When I can't even talk to my own friends reliably, I've got a problem.
<kentonv>
ocdtrekkie: I think there's a valid argument that in the case of someone trying to hide from a stalker by blocking them, the behavior makes sense. Problem is, there are so many different reasons to block people, and they all call for different behavior.
<ocdtrekkie>
You can't hide from a stalker with a public post.
<ocdtrekkie>
Block should be effectively one directional: I do not want to see the person I blocked.
<ocdtrekkie>
If they're stalking, they should probably be banned or otherwise dealt with, but they can just create additional accounts anyways.
<paulproteus>
So I'm planning on moving the vagrant-spk tutorial into a URL like something.readthedocs.org.
<paulproteus>
Possibly this should be sandstorm.readthedocs.org, rather than vagrant-spk.readthedocs.org.
<paulproteus>
I should probably get input on this before I actually commit to one or the other, but wanted to remark it's a thing on my mind.
ragesoss_ has quit [Ping timeout: 245 seconds]
ragesoss has joined #sandstorm
<zarvox>
I could believe that the packaging guide would be a part of sandstorm.readthedocs.org, but it would not be the front-and-center thing. That should be reserved for people trying to use or run a Sandstorm instance, not packagers.
<zarvox>
Of course that role is kinda played by our wiki at present.
<paulproteus>
I agree re: not front and center. I'd love to have the dev docs & the user docs to live in the same docs site, and so the front page would be like "Want to run a Sandstorm on a server? Follow this link; or want to package an app? follow this link"
<paulproteus>
I'm not sure the dev docs & user docs need to be the same site for that to work, but might as well I figure. But anyway.
<zarvox>
i,i docs.sandstorm.io
<zarvox>
although that could be confused for Documents rather than Documentation
<paulproteus>
Yeah, exactly; I sent a note to sandstorm-dev about this too
<paulproteus>
I at least initially like the idea of using docs.sandstorm.io. kentonv might be concerned about hosting something as crazy as the random output of mkdocs on that site (though we could CSP it down!!)
<zarvox>
"clearly" we should take the same approach as blog.sandstorm.io and host it on sandstorm!
<paulproteus>
Yeah, honestly it would be great to have a MkDocs Sandstorm app.
<paulproteus>
Or a readthedocs.org/Sphinx Sandstorm app.
<paulproteus>
Trying to keep my yak chain relatively small today. (-:
<ocdtrekkie>
Re: docs.sandstorm.io is what you're going to run it on.
<ocdtrekkie>
In terms of maintainability and such.
judytuna has quit [Ping timeout: 246 seconds]
<paulproteus>
"what you're going to run it on" == "the domain it'll use" ?
<paulproteus>
ocdtrekkie: ^ just trying to make sure I understand
<ocdtrekkie>
No, I mean Mediawiki, Mediawiki on Sandstorm, link it to a Github Wiki, use some other software?
<ocdtrekkie>
My comment above made no sense, I assume the sense of my statement got autocorrected out.
<paulproteus>
: D
<paulproteus>
"Re: docs.sandstorm.io is what you're going to run it on." => "Re: docs.sandstorm.io the real question is what you're going to run it on."
<paulproteus>
?
<ocdtrekkie>
Possibly.
<ocdtrekkie>
I mean, you're going to add a other thing to maintain?
<ocdtrekkie>
Another*
<ocdtrekkie>
(my phone is agitating me.)
<ocdtrekkie>
Doing it in Sandstorm would be ideal for dogwood ingredients, but not sure if the MediaWiki port is up to the task for a potentially large and heavily used wiki.
<ocdtrekkie>
Dogwood? Seriously?
<ocdtrekkie>
BRB, murdering keyboard software.
<paulproteus>
ocdtrekkie: You make me LOL.
<paulproteus>
Just be careful not to introduce remote code execution.
<paulproteus>
Anyway I really like the idea of writing docs in a text editor and basically like the idea of using Markdown.
<XgF>
New fun: std::basic_string::operator=(basic_string&&) is no longer noexcept because it can throw length_error() if max_size() < size()
<XgF>
Note the craziness that max_size() < size() is a *legal* condition
<paulproteus>
Note: If you are building a new integration, you should build it as webhook. We suggest creating an OAuth application to automatically install and manage your users’ webhooks. We will no longer be accepting new services to the github-services repository.