Recently I came across the need to self-host a Git-cloud instance (like Github, but I’m really trying to be brand abstract). I came across@Anthony_G_Cyphers pointed me to Gitea and thought to myself “Hmm, if I could get Lifeboat to manage nginx and SSL for me, this would be perfect!”
Well. I did that. I, uh, put more time into building this feature than I had originally planned.
I wanted to build something to encourage using source control and offer it for free (even in the demo mode) to everyone. An upcoming build of Lifeboat will automate Git + Gitea installation and make it easy to configure the web interface with nginx and HTTPS. The goal: Anyone will be able to host their own Git-cloud using the tools in Lifeboat for free.
I’m hoping to find interested individuals who might want to test out the process. Once Gitea is installed there aren’t really options for Lifeboat to configure, but I definitely want to get feedback on the way everything is implemented. Perhaps there are scenarios I had not considered, or bugs, or perhaps I’ve made a bad choice for a setting and am unaware.
You know… those things that go racing through your mind when you’re unsure if something’s ready.
I welcome anyone interested in Git, especially anyone who’s not already using Lifeboat, to privately forum message or email me. Just in case of incompatible changes I’m not going to post a download link here. I wouldn’t want a casual reader to unintentionally have a conflict.
An update to this, and a call for round two, I was made aware that Gitea’s ownership is in a questionable state. I have finished transitioning Lifeboat to use Forgejo instead, and I just wanted to reach people who may have missed this the first time.
hi Tim, if this is an option to be installed by default on the servers please don’t doit, just add that as an option and let us choose what we want to install , as putting that could lead to some overhead on the server side plus another security part to maintain or an eventual security hole.
I use Gitea for years and I’m happy with it . does the job.
Git-cloud will be an Extra to install. Currently, Lifeboat handles installing Redocly. I built that for a customer. Think of it like a growing list of packaged software installs like some other control panels do. I’ve changed the Server Tools to have a new Extras category, and addon tools will appear there in the future.
I would definitely recommend installing Git + Forgejo onto its own box, not on your main web server. I have a new Pi kit on the way that I’m going to use as my new Git-cloud instead of Github. Ultimately, it will be my “dog food” test. I am eager & excited, confident in this experiment. If successful, I may arrange with a friend to make it an offsite backup.
As a side note, transitioning from Gitea to Forgejo is pretty easy for now. Forgejo aren’t promising it will be easy to transition for much longer. If you were interested in switching, sooner rather than later would be my recommendation.
