<rjBadger>
So I am really liking the sandstorm platform, but I am noticing that some apps are pretty out of date (Rocket.Chat and SharedLatex for example). How difficult is it to package up apps yourself, or is it just easier to stick with the out of date apps on the marketplace?
frigginglorious has joined #sandstorm
nicoo has quit [Remote host closed the connection]
nicoo has joined #sandstorm
frigginglorious has quit [Remote host closed the connection]
frigginglorious has joined #sandstorm
<xet7>
rjBadger: Sometime there was idea to update SharedLatex, but it's not done yet, there is link to that port at https://sandstormports.github.io . In general, I did think of moving unmaintained Sandstorm apps to Sandstormports and looking at updating them. Would you like to participate?
<xet7>
rjBadger: I don't think updating is hard, it just takes some time. It's just looking at Sandstorm port specific changes, keeping them, and applying newest code from upstream.
<rjBadger>
I'm a bit of a newbie when it comes to this, but if I can help sure
<xet7>
rjBadger: I'll look where Sandstorm RocketChat repo is
<rjBadger>
yea thats what I cant seem to figure out. im trying to build that locally using the sandstorm packaging tutorial for meteor apps, but keep running into issues. I was wondering what the previous package build proccess was like
<xet7>
rjBadger: I see from Sandstorm Rocket.Chat info that Rocket.Chat as been updated latest 2017 Feb 22
<xet7>
rjBadger: I see that from Sandstorm app info
<xet7>
rjBadger: It seems that Sandstorm RocketChat repo points to RocketChat upstream repo. I'll look at upstream repo issues why it has not been updated.
<rjBadger>
yea, it seems that upstream packages a sandstorm spk but its out of step with there other versions
<rjBadger>
Yea, thanks. I dug around the official repos abit and could find it. I know the default vagrant-spk dev step fails.
<rjBadger>
hmm, looks like there just giving up on updating it themselves. that sucks
frigginglorious has quit [Ping timeout: 248 seconds]
<xet7>
rjBadger: That's not a problem. Now that I found where Sandstorm support was removed, I can make fork to SandstormPorts and apply changes back.
<rjBadger>
awesome, they mentioned alot of sandstorm specific changes that they were maintaining. Guess that explains why the default packaging pipeline was not working.
<rjBadger>
yea that all sounds great. truthfully wekan is the reason I checked out sandstorm in the first place, and rocket chat was just a nice bonus. I would definatly be interested in helping anyway I can to make sure rocketchat stays up to date on sandstorm
<rjBadger>
I might be doing it wrong but trying to build rocket.chat with the meteor-spk keeps failing at the vagrant-spk dev step, so something is off i think.
<xet7>
did you include that PR that removed Sandstorm stuff?
<rjBadger>
hmm, probably did actually
<xet7>
One way would be to git checkout to commit before removal PR