davidb/docker_gitea
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

switch to using gitea/gitea:latest

Browse Source
This commit is contained in:
David Blacka 2023-12-03 19:05:27 -05:00
parent 299abd9304
commit 451ecc04ed
3 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.gitignore vendored Normal file
View File

@ -0,0 +1 @@
.vscode

14
README.md
View File

@ -1,17 +1,17 @@
# blacka.com gitea service
# `blacka.com gitea` service
This repo consists of some deployment files for running [gitea](https://gitea.io/en-us/), a Go-based git repository manager (think a Go-based simple github.com-like service.)
This repo consists of some deployment files for running [`gitea`](https://gitea.io/en-us/), a Go-based git repository manager (think of this as a Go-based simple <github.com>-like service.)
The idea here is to host a git repository and project management system, only because it is somewhat easy to do so, and this is better than just using [gitweb](https://blacka.com/cgi-bin/gitweb.cgi).
The idea here is to host a git repository and project management system, only because it is somewhat easy to do so, and this is better than just using [`gitweb`](https://blacka.com/cgi-bin/gitweb.cgi).
## Overview
This runs the actual application via a docker image published by the [gitea](https://hub.docker.com/r/gitea/gitea) project. However, we do need some integration with the host in order to run. The basic problems that we need to solve are:
This runs the actual application via a docker image published by the [`gitea`](https://hub.docker.com/r/gitea/gitea) project. However, we do need some integration with the host in order to run. The basic problems that we need to solve are:
1. How do we get our main Apache-based web server to get us to the internal web server that the docker image runs? We use Apache's `mod_proxy` for that.
2. How do we get SSH pushes/pulls to work. Ideally, one would be able to use a git url like `git@blacka.com/davidb/docker_gitea.git`. But to do that, we first need the host itself (zeke) to handle an ssh-session as `git`.
2. How do we get SSH pushes/pulls to work? Ideally, one would be able to use a git url like `git@blacka.com/davidb/docker_gitea.git`. But to do that, we first need the host itself (`zeke`) to handle a ssh-session as `git`.
The `gitea` documentation talks about using `docker-compose`, so we will basically do that. Although, `docker-compose` itself (a python program not really maintained by the Docker project) is mostly gone, `docker compose` (with a space) now works with a normal `docker-ce-cli` install.
The `gitea` documentation talks about using `docker-compose`, so we will follow that advice. Although, `docker-compose` itself (a python program not really maintained by the Docker project) is mostly gone, `docker compose` (with a space) now works with a normal `docker-ce-cli` install.
## Deployment Artifacts
@ -45,7 +45,7 @@ We can check to see if the container is running with `docker container ls`
Finally, get the webserver configured and reloaded:
1. Update the apache configuration with the `mod_proxy` config. Note that the gitea container doesn't really care *where* you mount the proxy URL. I'm putting it at <https://blacka.com/git>, myself.
1. Update the apache configuration with the `mod_proxy` config. Note that the `gitea` container doesn't really care *where* you mount the proxy URL. I'm putting it at <https://blacka.com/git>, myself.
2. Check that the config you just added won't break Apache, and reload if it looks OK
```bash

2
docker-compose.yaml
View File

@ -6,7 +6,7 @@ networks:
services:
server:
image: gitea/gitea:1.19
image: gitea/gitea:latest
container_name: gitea
environment:
- USER_UID=895