From 451ecc04ed9cec4008fb48eda9d9857b39e7a0e9 Mon Sep 17 00:00:00 2001 From: David Blacka Date: Sun, 3 Dec 2023 19:05:27 -0500 Subject: [PATCH] switch to using gitea/gitea:latest --- .gitignore | 1 + README.md | 14 +++++++------- docker-compose.yaml | 2 +- 3 files changed, 9 insertions(+), 8 deletions(-) create mode 100644 .gitignore diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..722d5e7 --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +.vscode diff --git a/README.md b/README.md index 850c14b..aed76d3 100644 --- a/README.md +++ b/README.md @@ -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 -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 , 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 , myself. 2. Check that the config you just added won't break Apache, and reload if it looks OK ```bash diff --git a/docker-compose.yaml b/docker-compose.yaml index f18ff29..28e6085 100644 --- a/docker-compose.yaml +++ b/docker-compose.yaml @@ -6,7 +6,7 @@ networks: services: server: - image: gitea/gitea:1.19 + image: gitea/gitea:latest container_name: gitea environment: - USER_UID=895