Container w/ NGINX & LetsEncrypt
转到文件
Daniel Wolf 2f4eafca21
Build Container Image / build_arm64 (push) Successful in 40s 详情
Build Container Image / build_amd64 (push) Successful in 43s 详情
Build Container Image / build_riscv64 (push) Successful in 53s 详情
Build Container Image / build_armhf (push) Successful in 1m21s 详情
Build Container Image / build_i386 (push) Successful in 40s 详情
Build Container Image / push_amd64 (push) Successful in 10s 详情
Build Container Image / push_i386 (push) Successful in 10s 详情
Build Container Image / push_arm64 (push) Successful in 10s 详情
Build Container Image / push_armhf (push) Successful in 10s 详情
Build Container Image / push_riscv64 (push) Successful in 11s 详情
Build Container Image / build (push) Successful in 1m27s 详情
Build Container Image / push (push) Successful in 1m31s 详情
Build Container Image / update_readme (push) Successful in 9s 详情
ci: change branch image names
2024-03-27 23:22:31 -04:00
.gitea/workflows ci: change branch image names 2024-03-27 23:22:31 -04:00
.reuse chore: better reuse compliance 2024-03-27 22:45:40 -04:00
LICENSES add reuse copyright information 2023-10-25 11:04:05 -04:00
override chore: better reuse compliance 2024-03-27 22:45:40 -04:00
.dockerignore update *ignore files 2023-10-25 10:50:07 -04:00
Dockerfile refactor: rewrite ci workflows 2024-03-27 22:46:31 -04:00
LICENSE.md update license #noci 2024-03-09 09:38:45 -05:00
README.md update readme 2024-03-06 11:24:12 -05:00
docker-compose.yml add reuse copyright information 2023-10-25 11:04:05 -04:00

README.md

Git | Docker | unRAID

NGINX Reverse Proxy/Web Server

This docker container manages the NGINX application, a lightweight web server and reverse proxy. It includes certbot/letsencrypt for easily obtaining TLS certificates if your server is publicly accessible.

The latest tag points to version 1.25.4 and this is the only image actively being updated. There are tags for older versions, but these may no longer be using the latest Alpine version and packages.

This container is primarily intended to be used as a reverse proxy/cache to access other containers. You can certainly serve static content, but tools like PHP or MySQL are not included.

Docker-Compose

This is an example docker-compose file:

services:
  nginx:
    image: nephatrine/nginx-ssl:latest
    container_name: nginx
    environment:
      TZ: America/New_York
      PUID: 1000
      PGID: 1000
      ADMINIP: 127.0.0.1
      TRUSTSN: 192.168.0.0/16
      DNSADDR: "8.8.8.8 8.8.4.4"
      SSLEMAIL: 
      SSLDOMAINS: 
      B_MODULI: 4096
      B_RSA: 4096
      B_ECDSA: 384
    ports:
      - "80:80/tcp"
      - "443:443/tcp"
      - "443:443/udp"
    volumes:
      - /mnt/containers/nginx:/mnt/config

Server Configuration

These are the configuration and data files you will likely need to be aware of and potentially customize.

  • /mnt/config/etc/mime.type
  • /mnt/config/etc/nginx.conf
  • /mnt/config/etc/nginx.d/*
  • /mnt/config/www/default/*

Modifications to some of these may require a service restart to pull in the changes made.