Replace Caddy with Nginx and generate self-signed SSL certificate #300
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this branch, I updated our production deployment configuration to use Nginx instead of Caddy. In addition to updating the "docker compose" file and a "readme" file, it involved defining an "Nginx configuration file" and writing a script that generates a self-signed SSL certificate. The self-signed SSL certificate will be used to encrypt traffic between Cloudflare and the VM. Cloudflare will present a different, valid SSL certificate to end users.
There is room for improvement in this branch (e.g. re-organizing the files so they are not all in a top-level directory named
docs
). Given my availability this week, I want to get this merged in already. I'll file a separate ticket (assigned to myself) about re-organizing the files.