Update README.md

This commit is contained in:
Emil Shanaty
2026-02-03 23:46:08 +03:00
committed by GitHub
parent a984b1c7d3
commit 46d47307ad
+10 -5
View File
@@ -1,9 +1,9 @@
# TLS Certificates for Nginx (Development / Self-Signed) # TLS Certificates for Nginx (Development / Self-Signed)
In production, TLS certificates are typically issued by a trusted Certificate Authority (for example, via Let’s Encrypt). In production, TLS certificates are typically issued by a trusted Certificate Authority (for example, via Let’s Encrypt). For local development and demo environments, a self-signed certificate can be used.
For local development and demo environments, a self-signed certificate can be used.
## Generate a self-signed certificate (Linux/macOS) ## Generate a self-signed certificate (Linux/macOS)
From the repository root: From the repository root:
```bash ```bash
@@ -17,16 +17,21 @@ openssl req -x509 -newkey rsa:4096 \
``` ```
## Verify ## Verify
```bash ```bash
openssl x509 -in deploy/shagram/nginx/certs/cert.pem -noout -text | head openssl x509 -in deploy/shagram/nginx/certs/cert.pem -noout -text | head
``` ```
## Usage ## Expected files
The Nginx configuration expects:
The Nginx configuration expects these files to exist:
- `deploy/shagram/nginx/certs/cert.pem` - `deploy/shagram/nginx/certs/cert.pem`
- `deploy/shagram/nginx/certs/key.pem` - `deploy/shagram/nginx/certs/key.pem`
Start the deployment: ## Usage
After generating the certificate, start the deployment:
```bash ```bash
cd deploy/shagram cd deploy/shagram