me/env-docker
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Finish a working example.

Browse Source
This commit is contained in:
Hyperling
2023-07-05 20:02:50 -07:00
parent 6ce636f1d1
commit 67a1f3cd0c
3 changed files with 33 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
Config/ReverseProxy/config/conf.d/example.conf
View File

@ -2,11 +2,24 @@
# A dummy test file since true scripts are being kept private.
# This should help anyone understand how the project is being used.
## Instructions ##
# Add this without the comment to your /etc/hosts to test that it is working,
# YOUR_DOCKER_SERVER_IP example.com
# If testing locally on a workstation,
# 127.0.0.1 example.com
# Then to test, first start the container,
# cd $DOCKER_HOME/Config/ReverseProxy && docker compose build && docker compose up -d
# Then from the system with the modified /etc/hosts,
# curl --insecure example.com
# You should a blip in the log of the container as well as the contents of the
# proxied website in the terminal, NOT example.com. If using a browser then you
# should notice that the URL is still example.com but the website is correct.
# Force HTTPS
server {
listen 80;
server_name example.hyperling.com;
server_name example.com;
# Redirect to a more secure protocol.
return 301 https://$host$request_uri;
@ -16,13 +29,12 @@ server {
# Serve Resource
server {
listen 443 ssl http2;
server_name example.hyperling.com;
listen 443 ssl;
server_name example.com;
# These are only necessary if you are redirecting somewhere internal. If you
# paxx the user to a
ssl_certificate /usr/local/etc/letsencrypt/live/example.hyperling.com/fullchain.pem;
ssl_certificate_key /usr/local/etc/letsencrypt/live/example.hyperling.com/privkey.pem;
# The certs being used for the website.
ssl_certificate /etc/nginx/certs/example.com/cert.crt;
ssl_certificate_key /etc/nginx/certs/example.com/cert.key;
# Send traffic to upstream server
location / {
@ -42,8 +54,8 @@ server {
# Or alternatively, do it like the force of HTTPS:
#return 301 https://website.name/URI;
# So this should forward you from 'example.hyperling.com' to a real site:
proxy_pass https://cahlen.org;
# This should forward you from 'example.com' to a real site:
proxy_pass https://hyperling.com;
}
}