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
<ocdtrekkie>
isd: with regards to my Docs style change, I'm gonna have to figure out how to pull it out of theme.css. I don't want to edit that nightmare file, especially when the whole override system is already in place. I'll play with another PR Soon(TM) since Firefox dev console doesn't really help me here.
<isd>
We should set up the github action to build the docs on pr and spit the result out as an artifcat, so folks can look at it without merging or building it themselves.
<isd>
It would be nice for it to automatically preview somewhere, but that would be a good first step I think, and useful on its own.
<abliss>
I had an action that automatically previewed every PR, but it only works if the PR comes from someone attached to the main repo (not a fork), since it requires access to the secret password required to push to the staging area.
<isd>
Yeah, I think I remember the discussion.
<isd>
I think not actually previewing and just spitting out a zip with the files would be useful.
frigginglorious has joined #sandstorm
frigginglorious has quit [Remote host closed the connection]
_whitelogger has joined #sandstorm
<ocdtrekkie>
Can we just not care about the secret and encode it plain-style for a test grain? Or, crazy idea, how complex is GitWeb's grain data? Could we... generate a GitWeb grain backup as the artifact?
<ocdtrekkie>
I think GitWeb's data is pretty much just "the git repo". So I kinda wonder how difficult it would be to have the Action create a git repo, put in the right folder structure and metadata, and zip it up as a GitWeb grain.
<ocdtrekkie>
The change I PR'd today I would've needed to do as well anyways, so no harm in my little badly-tested PR. But I definitely wouldn't mind an easier testing strategy.
<ocdtrekkie>
Also, we need to change the generate directions/scripts to use Python3.
<ocdtrekkie>
mkdocs 1.1's primary blocker for us is probably just that.
xet7 has joined #sandstorm
michaeln3 has quit [Remote host closed the connection]
michaeln3 has joined #sandstorm
frigginglorious has joined #sandstorm
frigginglorious has quit [Ping timeout: 256 seconds]
frigginglorious has joined #sandstorm
michaeln3 has quit [Remote host closed the connection]
<isd>
It is pretty much just the git repo.
<isd>
I'm not sure how much value I think that adds though; I feel like it would be more annoying to have to upload the grain somewhere and do static publishing than to just extract the files and look at them.