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
wings has quit [Ping timeout: 260 seconds]
wings has joined #sandstorm
wings has quit [Ping timeout: 244 seconds]
wings has joined #sandstorm
wings has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
wings has joined #sandstorm
wings has quit [Client Quit]
ub3g33k has joined #sandstorm
<JacobWeisz[m]>
Ian, would it be pretty straightforward to add the environment variables needed to fully script the install? It looks like desired Sandcats name is already in there.
<JacobWeisz[m]>
I think we'd mostly just need to add the email address since it wouldn't be pre-registered.
<abliss>
Hey Ian Denhardt , were you looking at upgrading ttrss at some point? if so, what's the status?
<isd>
ocdtrekkie: I can't imagine it would be too bad, though I haven't dug deeply into the install script.
<isd>
abliss: It's still in the pipeline, yeah. I've been spreading myself too thin.
<isd>
It's more than just an update though; trying to integrate with the powerbox as well, and I haven't really figured out what an upgrade path should look like if it otherwise seems like a reasonable thing.
<JacobWeisz[m]>
I am gonna maybe look at the install script myself, see if I can maybe copy the existing environment variable behavior for any additional inputs needed.
<JacobWeisz[m]>
If we can get that, it'd be very high value for new deployments, particularly with people interested in doing a lot of Sandstorm deployments.
<isd>
Yeah
<isd>
Like I mentioned on the issue, you could just feed the prompt responses in via a file on stdin. But it kinda sucks to need to do that.
<JacobWeisz[m]>
I need to just like... spin up some VMs and play, knowing I don't actually care if the routing for outside access works at the end of testing in my case, since I'm just testing setting up Sandcats config right.
<JacobWeisz[m]>
And that would break any time we adjust the install flow, though I suppose we currently almost never do that.
<abliss>
Ian Denhardt: any chance you could easily cleave off the "update ttrss" part from the "add powerbox" part, and upload the former somewhere?
<isd>
Might be a little fiddly; I hit some merge conflicts when I tried to pull the latest from upstream into Jason's branch.
<isd>
So the big I'm working on also hasn't folded in other changes that needed to happen to get e.g. the API stuff to work.
<isd>
s/big/branch/
<abliss>
I'm thinking about adding a mechanism to periodically copy the user's "published articles" rss.xml to the static-hosting directory. But then I thought I should probably do so after the upgrade. Is your branch in a state where I could jump in and start trying to fix the API? or would that get in your way?
<isd>
I suspect they're mostly orthogonal; feel free.
<abliss>
ok, are you hacking on master at github.com/zenhack/ttrss-sandstorm?