Always 💖

Don't make me tap the sign

```
ssl_certificate /etc/path/to/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/path/to/privkey.pem; # managed by Certbot
}
```
Be sure to link it in your `sites-enabled` and restart nginx.

Also, hopefully this thing is readable, 300 characters per post is *not* a lot.

```
# Required for WebSocket to work
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
```

```
location / {
# Pass information to proxy
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;

proxy_pass 127.0.0.1:3000;
```

```
# For certbot to do its thing
location /.well-known/acme-challenge/ {
proxy_pass http:://127.0.0.1:3000/$request_uri;
}
}

server {
listen 443 ssl;
listen [::]:443 ssl;

server_name bluesky.example.xyz;
```

II. Nginx file
Your Nginx file should look something like this:
```
server {
listen 80;
listen [::]:80;

server_name bluesky.example.xyz;

location / {
return 301 $host$request_uri;
}
```

3. Edit `/etc/systemd/system/pds.service` to launch with the `--remove-orphans` option):
`ExecStart=/usr/bin/docker compose --file /pds/compose.yaml up --detach --remove-orphans`
4. Restart `pds.service`:
`systemctl restart pds.service`

I. Get rid of Caddy
1. Open the file `/pds/compose.yaml`
2. Comment out the lines dealing with Caddy or just delete them:
```
caddy:
some stuff
```

Little guide for anyone trying to set up a Bluesky instance with nginx.

Okay, I *finally* got everything set up and working with my Bluesky instance on my server! I am on Bluesky!