Re: Finding new home for our builds and other security sensitive stuff
On Mon, Mar 07, 2022 at 12:11:37PM +0100, Bastian Blank wrote:
> On Sun, Mar 06, 2022 at 04:40:24PM -0800, Noah Meyerhans wrote:
> > Are you not satisfied that the salsa issues have been addressed with the
> > latest maintenance? We are now running a current Gitlab release, at
> > least.
>
> I was talking about a Vault for our secrets. That's the priority now.
At the moment, yes, but earlier in the thread was discussion of needing
~50 GB of storage and a private Gitlab instance. That's the scenario I
want to avoid. It's bad enough that Debian owns one Gitlab
installation. A second one isn't going to reduce the burden of doing
so.
> But yes, I know that none of the issues with Salsa have been addressed
> in any way. They did an upgrade to Bullseye, so the database version is
> new enough now. But even this problem will show up again and again.
And why would that not be the case with a team managed Gitlab instance?
We as a team don't have experience running Gitlab, and it's really not
in our collective area of interest or expertise. *You* may be
interested in running a private Gitlab instance, but that just makes you
a single point of failure for such an instance and sets us for having to
deal with an unmaintained or poorly maintained instance in the future
should your involvement with the team change for any reason.
noah
Reply to: