Self Host Your Own Git Repository With Gitea!!
ฝัง
- เผยแพร่เมื่อ 30 ก.ย. 2024
- this is probably something i should have done long ago which is to self host my own git repository for personal programs i have written throughout the years, this is so usefule i just can't explain!
○○○ LINKS ○○○
Gitea ► about.gitea.com/
Raspberry Pi ► amzn.to/3vYUeHs
○○○ SHOP ○○○
Novaspirit Shop ► teespring.com/...
Amazon Store ► amzn.to/2AYs3dI
○○○ SUPPORT ○○○
💗 Patreon ► goo.gl/xpgbzB
○○○ SOCIAL ○○○
🎮 Twitch ► / novaspirit
🎮 Pandemic Playground ► / @pandemicplayground
▶️ novaspirit tv ► goo.gl/uokXYr
🎮 Novaspirit Gaming ► / @novaspiritgaming
🐤 Twitter ► / novaspirittech
👾 Discord chat ► / discord
FB Group Novaspirit ► / novasspirittech
○○○ Send Me Stuff ○○○
Don Hui
PO BOX 765
Farmingville, NY 11738
○○○ Music ○○○
From Epidemic Sounds
patreon @ / novaspirittech
Tweet me: @ / novaspirittech
facebook: @ / novaspirittech
Instagram @ / novaspirittech
DISCLAIMER: This video and description contains affiliate links, which means that if you click on one of the product links, I’ll receive a small commission.
Gitlab also has a self hosted version. Please do a review on how to install and configure it.
I've been using gitea for years. I don't run any code, but it's great for backing up my notes. I have a separate repository set up for each of my directories of notes. And for each project I use the readme for my own little pasebin for common commands. Just go to the repository and copy the commands. It's super convenient.
Oh....this is way easier with Portainer than with manual docker compose up.
Huh. I will have to re-examine this when I get home from work tonight.
Thanks.
How did you add the other apps in Portainer?
Installed Gitea yesterday on a raspberry pi 5 with docker after seeing your video! Really cool!
I did this recently and it works very well on a raspberry pi 3.
I don't have access to my local router so i use tailscale funnel - it's really nice and simple to share when using the latest version.
Really like seeing all your testing of different solutions like this. Have you ever tried or know of an open source version of Nessus or other vulnerability scanners for your environment?
Forejo is a better fork of this project. Gitea's assets were transferred to a for profit company 2 years ago without informing the public and bugfixes have slowed down just like they did with Gogs of which Gitea is a fork of.
I have a "problem" with Forejo. While I may have just enough knowledge to power up Gitea for basic use at TrueNAS using TrueCharts, I don't have it to launch Forejo. But hope the migration process is easy and at the future I may be able to transition.
Looked into Forejo, and it does seem like a better option than Gitea. Thanks for sharing.
I just have a local repo and a server repo, I share the folder of the server repo using Windows-sharing or Samba or NFS, etc. What extra functionality would gitea give me over my simple setup?
Versioning?
why not just use a gitlab? self hosted I mean. I did. But I am quite surprised how heavy this VM is with all the db etc inside. Still better than public hosting.
I do the same, I have gitlab on a vm on my esxi at home. than I learned how to upgrade it....ahahaha
@@g.s.3389 the best about having git is possibility to use different computers to work on the same project. I am completely not using the "work in group" feature but syncing between laptops/workstations is perfect for me
Privacy in code
I also use the community edition of GitLab running in an openSUSE VM on XCP-NG. One of the reasons I prefer GitLab is easy project export/import between GitLab instances. This, with their well-documented API, allowed me to migrate a MacGyver system of manual notes and local git repositories to a temporary GitLab instance. I then cleaned and made adjustments to the projects before export/import to a production GitLab instance.
And yes, before this GitLab adventure, I did experiment with Gittea and Gogs.
sometime, gitlab is too heavy for just saving projet code on git server
Thanks for introducing this. I set it up 2 weeks ago and I love it.
in my portainer gitea was not showing and portainer was up to date so had do do some workaround for the docker compose setup. that info i thought was missing from this video otherwise its a ocol setup and i have implemented one myself after your recommendation because i has similar use cases . thank you!
Hi! Would you be so kind and paste your compose yaml? Struggling a bit here
@@beavermexicano sure . will do so.
```
version: "3.9"
services:
gitea:
container_name: gitea
hostname: gitea
image: gitea/gitea:latest
environment:
- USER_UID=1000
- USER_GID=1000
- GITEA__database__DB_TYPE=mysql
- GITEA__database__HOST=mariadb:3306
- GITEA__database__NAME=giteaUsername
- GITEA__database__USER=giteaDBName
- GITEA__database__PASSWD=giteaPassword
restart: unless-stopped
volumes:
- ./gitea:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "8031:3000"
- "8032:22"
networks:
- containers
networks:
containers:
name: containers
external: true
```
@@beavermexicano i think youtube is deleting some comments. did you get the compose.yaml copy ?
trying again here -
```
version: "3.9"
services:
gitea:
container_name: gitea
hostname: gitea
image: gitea/gitea:latest
environment:
- USER_UID=1000
- USER_GID=1000
- GITEA__database__DB_TYPE=mysql
- GITEA__database__HOST=mariadb:3306
- GITEA__database__NAME=giteaUsername
- GITEA__database__USER=giteaDBName
- GITEA__database__PASSWD=giteaPassword
restart: unless-stopped
volumes:
- ./gitea:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "8031:3000"
- "8032:22"
networks:
- containers
networks:
containers:
name: containers
external: true
```
@@beavermexicano
```
version: "3.9"
services:
gitea:
container_name: gitea
hostname: gitea
image: gitea/gitea:latest
environment:
- USER_UID=1000
- USER_GID=1000
- GITEA__database__DB_TYPE=mysql
- GITEA__database__HOST=mariadb:3306
- GITEA__database__NAME=giteaUsername
- GITEA__database__USER=giteaDBName
- GITEA__database__PASSWD=giteaPassword
restart: unless-stopped
volumes:
- ./gitea:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "8031:3000"
- "8032:22"
networks:
- containers
networks:
containers:
name: containers
external: true
```
@@beavermexicano
here you go ...
version: "3.9"
services:
gitea:
container_name: gitea
hostname: gitea
image: gitea/gitea:latest
environment:
- USER_UID=1000
- USER_GID=1000
- GITEA__database__DB_TYPE=mysql
- GITEA__database__HOST=mariadb:3306
- GITEA__database__NAME=giteaUsername
- GITEA__database__USER=giteaDBName
- GITEA__database__PASSWD=giteaPassword
restart: unless-stopped
volumes:
- ./gitea:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "8031:3000"
- "8032:22"
networks:
- containers
networks:
containers:
name: containers
external: true
probably 1 year that i use gitea, great projet
Come aggiornare un contenitore gitea all'ultima versione senza perdere il database sqlite ?
you need to create persistant storage for your database. It means your database ( for example mysql data) needs to be mounted to a volume that holds data even if container is recreated.
Other cleaner way is to use separate containeer for databse and gitea. This way no matter how many times you do what operations to your gitea container your data stays safe in your mysql container.
Search "persistant mysql storage for dockers" in your search engine to start. That might help more.
Hell yeah!
why not just use a private github repo?
Privacy
Are you sure only you can see the private repo? Cannot be repeated enough time: if a service is free you are the product.
First 😂
I like your videos. but I keep giving you dis-likes cuz of the intro music 😀