Making PopSpace a standalone deploy about popspace

[a-type]

Oh yeah, I did let that work fall by the side, thanks for reminding me.

That branch is basically ready to go, we did some testing internally. Maybe I'll go ahead and merge it. It covers both a local SQLite db and on-volume file storage.

[a-type]

oops, I forgot the original plan was just to run LiveKit locally, too. that might still be feasible! Still, LiveKit's cloud offering is really nice and has a pretty good free tier. I'd recommend checking it out for now!

[dillfrescott]

I would love to see this happen one day! Sounds awesome! <3

[vbbjandrade]

Hey, just wondering if there has been any progress on this. From what I have seen there is a "sqlite" branch with some of the adjustments mentioned.
My organization has been looking for a solution like PopSpace for a while, but the S3 requirement is keeping us from using it. Thanks!

[a-type]

Ok, I don't have much time at the moment, but here's my checklist...

• Update README with the new local file / SQLite changes
• Build and push the new container image

[a-type]

I should have known better than to make a checklist for myself while on parental leave!

But I did finally get around to updating the README and pushing that new image. The new image should no longer require S3 or Postgres, all you need to do is provide LiveKit or Twilio credentials and expose the necessary ports.

This makes Popspace mostly standalone. In theory we could also support direct WebRTC media and remove the external media service requirement! So I'll leave this issue open, although truthfully I don't think I have time to pursue that in the foreseeable future, and my experience with WebRTC for larger groups indicates it would not scale past like 5 users.