4get-apache/README.md
2025-01-07 10:11:00 -05:00

62 lines
1.7 KiB
Markdown

# 4get-apache
Dockerfile and compose for 4get bleeding edge, with PUID, PGID and port config.
## Why?
1. I wanted to learn how to build a custom docker image
2. The official 4get image takes forever for updates
3. There is no PUID, PGID or port configuration on the official image
I kept the structure pretty simple, so hey, it might help another noob learn Dockerfile
## Dockerfile
Simply ```git clone``` this repo:
```bash
git clone https://git.plunked.party/tony/4get-apache
```
and then run ```./rebuild```:
```bash
cd 4get-apache/
chmod +x ./rebuild
./rebuild
```
## Docker Compose
Here's an example docker-compose.yaml for the service:
```yaml
services:
fourget:
container_name: fourget
image: fourget-apache
restart: ${RESTART_MODE}
environment:
# Replace with your stuff
- FOURGET_SERVER_NAME=4get.plunked.party
- FOURGET_SERVER_LONG_DESCRIPTION="PLUNKED!!!!"
- FOURGET_SERVER_SHORT_DESCRIPTION="click here 4 sum fun."
- FOURGET_BOT_PROTECTION=0
- FOURGET_DEFAULT_THEME="Dark"
# My additions
- PUID=${FOURGET_ID}
- PGID=${FOURGET_ID}
- PORT=6969
volumes:
# Optional, for custom banners and home.html
- ./4get/banner:/var/www/html/4get/banner
- ./4get/template/home.html:/var/www/html/4get/template/home.html
ports:
- '6969:6969'
```
There's some startup verbose when running ```docker compose logs```.
## HTTPS Notice
The included httpd.conf doesn't include a HTTPS setup.
If you're unfamiliar with this stuff, I would recommend using [Nginx Proxy Manager](https://github.com/NginxProxyManager/nginx-proxy-manager) and
setting up HTTPS there.
You can then reverse proxy to your 4get service through your domain with HTTPS certs.