02:21 <rjBadger> its not possible to install sandstorm on freebsd, correct?

02:35 <isd> rjbadger: correct. Unfortunately the syscalls we use for sandboxing are very Linux-specific.

02:41 <rjBadger> thats what I remembered. Slightly off topic question then, is there a way to host Weekan on freebsd?

02:43 <isd> xet7 would be the one to ask.

02:44 <isd> He's probably asleep at this hour though.

02:44 <rjBadger> ok thanks though

02:45 <isd> best of luck.

03:30 <rjBadger> Ok slightly different question. Can you install sandstorm on alpine linux?

03:35 <isd> Haven't tried it but I don't see why not.

03:36 <isd> The distro shouldn't really matter.

03:48 <rjBadger> well alpine by default does not have useradd so thats tripping it up right away

03:55 <isd> If you can get it past the install I think it should be smooth sailing from there; Sandstorm basically bundles its own rootfs and only really interacts with the kernel when running.

03:56 <rjBadger> alpine uses adduser, i dont think useradd is in the repo.

03:56 <isd> Ah.

03:57 <isd> Looking at the script apparently it was written to use useradd because adduser was supposedly debian specific...

03:57 <isd> maybe we could fall back to one of the other isn't present.

03:58 <rjBadger> might help with alpine

03:59 <rjBadger> alpine also uses musl libc which i thought would be the next stumbling block, but it sounds like sandstorm is pretty isolated from the rest of the system.

03:59 <isd> I believe it will also work correctly if you create the user you're going to run it as ahead of time.

04:00 <isd> Yeah, I wouldn't be surprised if there were some hiccups building against musl, because I don't know if anyone's tried it, but installing the bundle it shouldn't matter what the system libc is.

04:01 <isd> The install script basically downloads an isolated chroot environment for sandstorm, so it's not using anything on your filesystem really.

04:03 <rjBadger> what user do i need to create?

04:04 <isd> Whatever you tell it to run the server as. If you tell it to use the defaults it chooses 'sandstorm' as the name.

04:15 <isd> Opened an issue for the adduser thing: https://github.com/sandstorm-io/sandstorm/issues/3272

04:18 <rjBadger> hahaha, yes its installed, though the adduser thing probably will trip someone else up. thank you so much for your help

04:19 <isd> no problem.

04:54 <rjBadger> so rocketchat still hasnt updated for sandstorm huh. thats a shame

07:09 <xet7> rjBadger: Wekan FreeBSD: https://github.com/wekan/wekan/issues/2662

07:12 <xet7> rjBadger: rocketchat removed Sandstorm support, because it was complex to support. It does not make sense to update RocketChat yet, because they are doing major changes by adding Apollo etc.

08:28 <isd> Complex to support and also Sandstorm wasn't really active at the time. But yeah, iirc it was more challenging than just bumping the version number.

11:50 <xet7> At that time there was a lot of features added to RocketChat, and to keep RocketChat running at Sandstorm did require a lot of workarounds. There is still possibility to sometime try to merge Sandstorm specific code back to RocketChat, there is pull request etc git history, it just would need a lot of testing etc.

11:51 <xet7> RocketChat also has a lot of code, it starts slower than Wekan

11:51 <xet7> Both Wekan and RocketChat are made with Meteor

11:51 <xet7> Sometimes there was discussion that should some other lighter chat app be the default

11:52 <xet7> like SandChat

11:52 <xet7> although it has a lot less features

11:52 <xet7> AFAIK nobody has yet tried to port Mattermost to Sandstorm

11:53 <xet7> I'm not sure do I remember correctly, was there even RocketChat feature that RocketChat could embed some other Sandstorm grain. Or was it some other app.

12:03 <abliss> yeah that's rocket.chat and it's super cool