We are changing our system. We settled on git (but are open for alternatives) as long as we can selfhost it on our own machines.

Specs

Must have

  • hosted on promise
  • reliabile
  • unlikely to be discontinued in the next >5 years
  • for a group of at least 20 people

Plus

  • gui / windows integration
  • The Bard in Green@lemmy.starlightkel.xyzEnglish
    4·
    4 months ago

    We’re also using Forgejo for a small consulting team working on lots of different projects for a lot of different clients.

    A couple of our team members who came from a more complex and scaled environment (particularly our DevOps / SRE guy who’s worked at such places as LinkedIn and Snowflake) want to move us to Gitlab because it’s “more powerful” but I like Forgejo because it’s just super simple. Just does exactly what I need, doesn’t give me to many more options.

    We have

    • Projects segregated into teams, organized by client (so only those working on a specific client’s projects have access to their repos).
    • Able to invite clients and put them into the team for their project (we’ve had a couple clients that want that).
    • Able to automate deployments with webhooks (this was pretty easy to get working).

    One of our devs wanted to use Actions. It’s hard to get that working and (at least a month ago) there were warnings that Actons aren’t mature yet and are probably insecure (looks like that may have changed with the recent jump to Forgejo 8.0). I think it’s now a non issue for us though because we were like “Dude, stop trying to role your own CI/CD, that’s why we have two infrastructure people!”