2026-11-09 06:20 UTC
Replies (4)
-
@CameronDev@programming.dev 2026-11-09 06:40
Ive run gitea and gitlab, they are both trivial to run. (Both probably have AI code, but in my experience gitlab has been rock solid). Search for docker compose instructions, they are generally the quickest and easiest way to get going: docs.gitlab.com/install/docker/installation/#inst… forgejo.org/docs/v15.0/admin/…/docker/#docker The upside of docker is that if the do push a bad version, its trivial to downgrade and use the previous version, just update the compose file and restart. But, If you really want to get on with game dev, just push to github/gitlab/codeberg. Theyll get you started way faster and you can worry about your own self hosted thing later when it matters more to you. Its easy to transfer between them later.
-
@hoover900@sh.itjust.works 2026-11-09 06:51
I’d recommend using Perforce over Git. Perforce in my opinion is easier to understand and use, as well as more widely used in the game industry. The big difference between the two is centralized vs decentralized, Perforce being centralized and Git being decentralized. Plainly put P4 is one server with clients checking files in and out from it and tracking those changes, where Git is multiple servers merging their changes together. In your use case here both are free to use. You should keep in mind that P4 wants to run on bare metal as you mentioned hosting this in your own server, so if you were thinking of spinning up something in proxmox or docker you may run into issues. Whatever you use, making sure you have meaningful commit messages is the most important thing, especially if you’re going to be working with others. A brief idea of why a file was a changed six months ago is much more helpful than a commit message that says “…” or “updated”.
-
@TheKracken@lemmy.world 2026-11-09 06:52
Check out this site gitmastery.me it makes it a game to learn git. There are some core concepts that are 90% of what you need to know. Most everything else is specific issues and strategies. If it’s just you.working on a project you can get away with learning commits, pushing, branching, and merging.
-
@Static_Rocket@lemmy.world 2026-11-09 07:36
This may sound terse, but I’m just trying to respect your time: You don’t need a server to start using git You don’t need a forge to host a git server (gitweb works fine for indexing, reading, and cloning). If you aren’t publishing anything then just play around locally with an IDE plugin for git or one of the listed GUIs git-scm.com/tools/guis If you ever do feel like publishing your work, it’s just a git remote add and git push away.