You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For documentation purposes, I'm following this guide composed by Claude.ai for installing and using a TLS certificate. Will document here any ways in which I diverge from it.
I decided to install nginx natively on the droplet server instead of using a Docker container version like the instructions suggested. This means I installed an available-site virtual host config that compliments the base nginx config located in nginx.conf.
I didn't think the overhead of Docker was really necessary for nginx and decided to keep this reverse proxy very thin to cut down on some resource usage. Eventually if we need to scale this, we'll need to reconsider this decision and move to a horizontally scalable reverse proxy for serving TLS certificates and other load balancing functionality.
Uh oh!
There was an error while loading. Please reload this page.
Suggestion / Feature Request
Description
We are working with sensitive data and user sessions, so this means we need to encrypt all user session traffic.
Requirements
refactor.engineer
domain is used as the site's production domain (already purchased)ubuntu-droplet1
(potentially not needed yet, TBD)http://refactor.engineer
always redirects tohttps://refactor.engineer
ubuntu-droplet1
The text was updated successfully, but these errors were encountered: