Conversation

Notices

1. Embed this notice
   Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Tuesday, 17-Dec-2024 20:13:40 JST Jan Wildeboer 😷:krulorange:

   So how stable and reliable is my #Forgejo instance that I am running as a rootless container on my server since quite a while? Well. Rock solid. Always there, always working, Uses a fraction of the resources that my #Gitlab test instance occupied. And I updated it every time a new release was published. It's just a simple stop container, pull updated container, start it again.

   I am VERY impressed and happy. Running your own forge is another step towards more decentralisation :)

   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Tuesday, 17-Dec-2024 20:21:17 JST Jan Wildeboer 😷:krulorange:

     in reply to

     And yes, I have donated money (and a bit if time) to the good folks working hard on making it better and better. If more people would do that too, we might see the planned federation features showing up sooner :) Imagine that! Being able to discuss issues and send pull requests with your ActivityPub/Mastodon Account! Post updates and status messages straight from teh Forge to your timeline here!

     https://forgejo.org

   • Embed this notice
     Psyhackological (psyhackological@fosstodon.org)'s status on Tuesday, 17-Dec-2024 20:25:15 JST Psyhackological

     in reply to

     @jwildeboer are you using reverse proxy and if so, which one?

   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Tuesday, 17-Dec-2024 20:53:15 JST Jan Wildeboer 😷:krulorange:

     in reply to

     Having a personal forge means I don't really have to care about scalability. It runs with the embedded SQLite engine just fine. No need for a complex setup with a separate database. Small is better :) I currently have 17 repositories in it, some of them are mirrors from GitHub repos, some are simple repos with Jekyll sources for my websites. I have all the repos also on my laptop and my home server, so even if everything explodes, I can restore everything I need.

   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Tuesday, 17-Dec-2024 20:58:55 JST Jan Wildeboer 😷:krulorange:

     in reply to

     This also means that I keep my forge hidden from the public, thus reducing traffic to it. I had it open for a few hours and in a matter of seconds the AI scraping bots and other scripts started hitting it. Traffic shot up to ridiculous levels. I didn't want to take care of all that shit, so I locked it down again. I am using #codeberg as a kind of proxy now. I mirror some repos there, so everyone can get the code there. Best I can do for now :(

   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Tuesday, 17-Dec-2024 21:02:27 JST Jan Wildeboer 😷:krulorange:

     in reply to

     (And yes, I am a paying member of the #Codeberg association since quite a while)

   • Embed this notice
     Marcos Dione (mdione@en.osm.town)'s status on Tuesday, 17-Dec-2024 21:28:37 JST Marcos Dione

     in reply to

     @jwildeboer I do the same for my own #nextcloud. It also makes it easier to backup (and restore) the db.

     Because you have backups, right? :)

   • Embed this notice
     🐈‍⬛David Sommerseth (dazo@infosec.exchange)'s status on Tuesday, 17-Dec-2024 22:02:45 JST 🐈‍⬛David Sommerseth

     in reply to

     • Codeberg

     @jwildeboer

     What would you say is the advantage of running a closed Forgejo instance vs just pushing your git trees to home server via SSH?

     I'm also using @Codeberg for public stuff (also donated too!) ... which is why I wonder about the advantage of also running a fully private instance.

   • Embed this notice
     Nils (thasl@social.tchncs.de)'s status on Tuesday, 17-Dec-2024 23:07:13 JST Nils

     in reply to

     @jwildeboer Thanks for your recent posts on that topic, was very helpful and pushed me to finally do the same :)
     How did you protect/hide your Forgejo instance? Just setting repos to private, or is there an additional layer, esp in front of the web app, like client certs or a proxy?