From: Denver Gingerich <denver@ossguy.com>
To: Overseers mailing list <overseers@sourceware.org>
Subject: Re: BBB instances
Date: Thu, 22 Sep 2022 22:23:33 +0000 [thread overview]
Message-ID: <20220922222333.GM5021@ossguy.com> (raw)
In-Reply-To: <31941a86-9387-21e1-1722-8550288671a4@gmail.com>
disclosure: One of my employers is Software Freedom Conservancy. I worked a bit on things related to SFC's BBB server, so thought I could help a bit here.
On Thu, Sep 22, 2022 at 01:27:36PM -0600, Elena Zannoni via Overseers wrote:
> Regarding the use of MongoDB, James tells me that we used something
> equal or earlier than mongodb-org 4.4.16, on Ubuntu. In 2020, we used
> Ubuntu 16 because BBB was working only on that version, so the MongoDB
> would have been whatever was available on that Ubuntu server.
I have some technical questions about that setup, which I'll follow up about off-list. I think digging too deep into BBB deployment discussion is (at best) premature for this list right now.
> On 9/21/22 1:47 PM, Bradley M. Kuhn via Overseers wrote:
> > Ian Kelling via Overseers wrote at 20:23 (PDT) on Tuesday:
> >> About BBB, It currently includes MongoDB in it's [sic] server software,
> >> which went nonfree a few years ago. You can still run an older version
> >> which is all free software
> >
> > Indeed, SFC's instance currently does this. We published our methodology on
> > how to do it as well. It's important to note that the main database that
> > BBB uses is Postgres, and MongoDB is only used for runtime session data.
>
> Do you have a link to the article?
The source with the description is linked from the main page of our BBB instance. In short, we are using the version of MongoDB from the stock distro repository rather than the MongoDB provided by BBB's repository, as it sounds like you are doing as well. It seems that few (if any?) distributions have even packaged the SS-Public-Licensed version of MongoDB. We're curious to know why upstream is pushing folks toward that version, but we didn't want to raise it upstream until we were ready to set aside time for wider BBB deployments, which we do hope to do soon -- possibly with Sourceware as a member project!
Denver
next prev parent reply other threads:[~2022-09-22 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 20:41 Elena Zannoni
2022-09-21 3:23 ` Ian Kelling
2022-09-21 19:47 ` Bradley M. Kuhn
2022-09-22 19:27 ` Elena Zannoni
2022-09-22 22:23 ` Denver Gingerich [this message]
2022-09-23 0:03 ` Ian Kelling
2022-09-25 23:04 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220922222333.GM5021@ossguy.com \
--to=denver@ossguy.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).