• Technology Consultant.
  • Software Developer.
  • Musician.
  • Burner.
  • Game Master.
  • Non-theistic Pagan.
  • Cishet White Male Feminist.
  • Father.
  • Fountain Maker.
  • Aquarium Builder.
  • Hamster Daddy.
  • Resident of Colorado.
  • Anti-Capitalist.
  • Hackerspace Regular.
  • Traveler of the American West.
  • 2 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 7th, 2023

help-circle

  • 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!”



  • This exact thing happened to one of my clients. And it sucked because they didn’t even register the domains with Ionos, they registered them with some other company that then got bought by Ionos. They were not technically savvy and didn’t understand what was happening until it was way too late. They lost about 8 domains closely associated with their business and with their CEO’s research.









  • Easy. I have servers that are only available on my local network and lots of different devices that I MIGHT want to use to access those servers. I haven’t bothered to make sure my key is on EVERY SINGLE DEVICE and some of them, I might not actually even WANT my key on as they’re not terribly well secured and they might leave my house (my Windows gaming laptop I haven’t used in six months comes to mind).

    But for cloud accessible servers… yeah.





  • I’m running my own instance, JUST so I can be in control of my own Lemmy experience (and in control of my own archive of my Lemmy activity). I’m not going anywhere anytime soon.

    Yes, my instance was down for three days last week. I had trouble with an update and didn’t have time to troubleshoot it. But I wanted my Lemmy so I DID get around to it and got it working again. And yeah… I never did get email working properly so when my ONE friend who’s not me joined my instance I had to command line into the database and approve him manually. But so what?

    And yeah, eventually the internet ecosystem may shift again, or I might get hit by a bus or who knows?

    But if you WANT to join a tiny instance that’s 99.999% (bus factor) not going anywhere for a while, I’d probably let you join mine.