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>
That is what I did to get it building against alpine, yes.
<isd>
Though I had to basically patch the spk manually do to the /proc symlink hack, because right now docker-spk doesn't use searchPath, it just bundles the docker image, and during the build /proc is mounted so we can't put stuff there.
<isd>
musl maintainer has expressed openness to a fallback realpath() for when /proc isn't available, so that's a possible path forward.
<JacobWeisz[m]>
\o/
wings has joined #sandstorm
_whitelogger has joined #sandstorm
xet7 has quit [Remote host closed the connection]
frigginglorious has joined #sandstorm
frigginglorious1 has joined #sandstorm
frigginglorious has quit [Ping timeout: 265 seconds]
frigginglorious1 is now known as frigginglorious
frigginglorious has quit [Remote host closed the connection]
TC01 has quit [Ping timeout: 240 seconds]
frigginglorious has joined #sandstorm
frigginglorious1 has joined #sandstorm
frigginglorious has quit [Ping timeout: 265 seconds]
frigginglorious1 is now known as frigginglorious
<isd>
ocdtrekkie: got asp hello world working.
TC01 has joined #sandstorm
<JacobWeisz[m]>
I see that. Woo!
frigginglorious has quit [Read error: Connection reset by peer]
frigginglorious has joined #sandstorm
frigginglorious has quit [Ping timeout: 240 seconds]
frigginglorious has joined #sandstorm
<isd>
I would be kinda neat to integrate Sandstorm with avahi/mdns somehow, so you could hook it up on a local network and do powerbox requests for printers or such using the regular discovery mechanisms.
<isd>
It would
<isd>
I guess you could probably make a driver grain for this.
<JacobWeisz[m]>
I assume you'd have to edit the network security panel to enable it to access them too?
<JacobWeisz[m]>
I have my Sandstorm server able to authenticate with an AD server on premise, so I definitely wouldn't be opposed to apps that interact with my local network.
<isd>
Maybe? It would be nice to be able to only have the mdns driver grain have this access, so I can still share access to other grains with people outside the network and not necessarily give them access to my local network.
<JacobWeisz[m]>
So perhaps system grains would be exempt from that panel, due to being more directly controlled by the server admin.