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

Eliminate the word should for will and need.

Browse Source
This commit is contained in:
Hyperling
2025-10-30 07:58:56 -07:00
parent 7dd2ef5e75
commit 2e4520d6ae
21 changed files with 48 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Config/ReverseProxy/README.md
View File

@@ -59,7 +59,7 @@ If the proxy needs turned off either stop or down may be used.
## Upgrade
Upgrading the containers should be as easy as this:
Upgrading the containers is as easy as this:
```
# docker compose down
@@ -93,4 +93,4 @@ If wanted as a one-line command:
1. Restart the project based on Update Config above.
1. (Optional) Now you may run the letsencrypt script for a real certificate.
1. (Optional) Run another Update Config to make sure the certs are loaded.
1. Done! If set up correctly the site should be live.
1. Done! If set up correctly the site will be live.

6
Config/ReverseProxy/config/conf.d/git.example.com
View File

@@ -1,6 +1,6 @@
# 2024-12-31 Hyperling
# A dummy test file since true scripts are being kept private.
# This should help anyone understand how the project is being used.
# This will 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,
@@ -11,9 +11,9 @@
# cd $DOCKER_HOME/Config/ReverseProxy && docker compose build && docker compose up -d
# Then from the system with the modified /etc/hosts,
# curl --insecure git.example.com
# You should see activity in the container log as well as the contents of the
# You will see activity in the container log as well as the contents of the
# proxied website in the terminal, NOT git.example.com. If using a browser then you
# should notice that the URL is still git.example.com but the website is correct.
# will notice that the URL is still git.example.com but the website is correct.
# Force HTTPS
server {

8
Config/ReverseProxy/config/conf.d/html.example.com
View File

@@ -1,6 +1,6 @@
# 2023-07-08 Hyperling
# A dummy test file since true scripts are being kept private.
# This should help anyone understand how the project is being used.
# This will 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,
@@ -11,9 +11,9 @@
# cd $DOCKER_HOME/Config/ReverseProxy && docker compose build && docker compose up -d
# Then from the system with the modified /etc/hosts,
# curl --insecure html.example.com
# You should see activity in the container log as well as the contents of the
# proxied website in the terminal, NOT html.example.com. If using a browser then you
# should notice that the URL is still html.example.com but the website is correct.
# You will see activity in the container log as well as the contents of the
# proxied website in the terminal, NOT git.example.com. If using a browser then you
# will notice that the URL is still git.example.com but the website is correct.
# Force HTTPS
server {

8
Config/ReverseProxy/config/conf.d/nextcloud.example.com
View File

@@ -1,6 +1,6 @@
# 2025-01-02 Hyperling
# A dummy test file since true scripts are being kept private.
# This should help others understand how to get Nextcloud working.
# This will help others understand how to get Nextcloud working.
## Instructions ##
# Add this without the comment to your /etc/hosts to test that it is working,
@@ -11,9 +11,9 @@
# cd $DOCKER_HOME/Config/ReverseProxy && docker compose build && docker compose up -d
# Then from the system with the modified /etc/hosts,
# curl --insecure cloud.example.com
# You should see activity in the container log as well as the contents of the
# proxied website in the terminal, NOT cloud.example.com. If using a browser then you
# should notice that the URL is still cloud.example.com but the website is correct.
# You will see activity in the container log as well as the contents of the
# proxied website in the terminal, NOT git.example.com. If using a browser then you
# will notice that the URL is still git.example.com but the website is correct.
server {
listen 80;

8
Config/ReverseProxy/config/conf.d/proxy.example.com
View File

@@ -1,6 +1,6 @@
# 2022-10-05 Hyperling
# A dummy test file since true scripts are being kept private.
# This should help anyone understand how the project is being used.
# This will 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,
@@ -11,9 +11,9 @@
# cd $DOCKER_HOME/Config/ReverseProxy && docker compose build && docker compose up -d
# Then from the system with the modified /etc/hosts,
# curl --insecure proxy.example.com
# You should see activity in the container log as well as the contents of the
# You will see activity in the container log as well as the contents of the
# proxied website in the terminal, NOT proxy.example.com. If using a browser then you
# should notice that the URL is still proxy.example.com but the website is correct.
# will notice that the URL is still proxy.example.com but the website is correct.
# Force HTTPS
server {
@@ -67,7 +67,7 @@ server {
# Or alternatively, do it like the force of HTTPS if not your server.
#return 301 https://website.name/$request_uri;
# This should forward you from 'proxy.example.com' to a real site:
# This will forward you from 'proxy.example.com' to a real site:
proxy_pass https://hyperling.com;
}

2
Config/ReverseProxy/config/html/README.md
View File

@@ -2,5 +2,5 @@
If the reverse proxy also serves static HTML sites, the root directories of each
can be placed here. Then in `../conf.d` add a file which points the domain to
the HTML web root, such as `/etc/nginx/html/www.website.name`. An example for
this exists called `html.example.com`. It should be fairly easy to recreate for
this exists called `html.example.com`. It is fairly easy to recreate for
another website.