History

* Add new area for defining upstream systems.

* Example file for demonstration domain.

* Use the new upstream hosts section.

* Do the proxy directives in the main file.

* Commit any final changes.

* Fix example resource name.

* Mention the need to have ports specified in the upstream file, not server block.

* Adjust formatting.

2023-07-09 16:02:47 -07:00

config

Fixes for Reverse Proxy Go-Live (#6 )

2023-07-09 16:02:47 -07:00

create_letsencrypt_certs.sh

Take into account anything with example.com as being an example.

2023-07-08 12:35:12 -07:00

create_placeholder_certs.sh

Add comment sections, use CERT_DIR, add exit 0.

2023-07-08 08:18:14 -07:00

docker-compose.yml

Create script to get real certificates. Programs are functional but have not tried pointing the production router to the test box yet to see if the challenge will pass.

2023-07-06 07:33:17 -07:00

Dockerfile

Fixes for Reverse Proxy Go-Live (#6 )

2023-07-09 16:02:47 -07:00

README.md

Remove "you" verbiage.

2023-07-08 12:49:26 -07:00

README.md

Initial Setup Instructions

How to first begin using this subproject.

Move to the directory of this README.
```
$ cd $DOCKER_HOME/Config/ReverseProxy
```
Add configuration files to ./config/conf.d/ which are named based on the domains and subdomains they point to.
Run the placeholder certificate program.
```
# ./create_placeholder_certs.sh
```
Make any personal changes to ./config/nginx.conf.
Build the project.
```
# docker compose build
```
Start the project.
```
# docker compose up -d
```

Verify it started correctly, no configuration file errors.

# docker logs reverseproxy-app-1
# docker logs reverseproxy-certbot-1

DO NOT

Edit any configurations or website data inside the container. It is destroyed on each build.
- Instead, modify the files in ./config/ then use the Update Config commands below.
Install any additional software inside of the container. It will not persist a down and up.
- Instead, add what is needed to the docker-compose.yml or Dockerfile to be done on each rebuild.
- Alternatively write a script such as ../Nextcloud/fixes.ksh which is run after every upgrade.

Other Commands

Tasks which will also likely come up while using this subproject.

Stop

If the proxy needs turned off either stop or down may be used.

# docker compose stop
# docker compose down

Upgrade

Upgrading the containers should be as easy as this:

# docker compose down
# docker compose pull
# docker compose build
# docker compose up -d

Update Config

Replace the configuration based on any new, updated, or removed files. This may be possible to do when the system is up, but the best results have come from going down and back up. This is essentially an upgrade but there is no pull.

# docker compose down
# docker compose build
# docker compose up -d

If wanted as a one-line command:

# docker compose down && docker compose build && docker compose up -d