Skip to content
Snippets Groups Projects

Add more configurations for reverse proxies

Merged Kio! requested to merge add-more-configs into main
All threads resolved!
1 file
+ 6
1
Compare changes
  • Side-by-side
  • Inline
@@ -274,6 +274,7 @@ Add these lines to your frontend:
```
And these to your backend:
```haproxy
backend sharkey-be
http-reuse aggressive
@@ -286,16 +287,17 @@ And these to your backend:
http-request set-header X-Forwarded-Proto https
server sharkey-server <ip>:3000 check observe layer7 error-limit 10 on-error mark-down inter 2s rise 10 slowstart 10s
```
Check out Latte Macchiato's [guide](https://blog.lattemacchiato.dev/how-to-make-your-fedi-instance-performance-not-suck/) to making your fedi instance suck for more optimization tricks with HAProxy.
### Traefik
> Heads up - Sharkey doesn't officially support Traefik, but you can still find community support for it within the discord.
Our configs will make the assumptions that sharkey is listening to port `3000`, your https(443) entrypoint is called ``webSecure`` and that you have a certificate resolver ready called ``myResolver``. Change these as necessary. Remember to change ``myshark.ey`` to your instances domain name.
#### Docker Labels
Append these labels to your sharkey service in docker-compose.yml:
```yml
...[your docker config]...
labels:
@@ -305,8 +307,10 @@ Append these labels to your sharkey service in docker-compose.yml:
- "traefik.http.routers.sharkey.tls.certresolver=myResolver"
...[your docker config]...
```
#### Dynamic Config
insert this into your dynamic config:
```yml
http:
routers:
@@ -328,6 +332,7 @@ http:
> Heads up - Sharkey doesn't officially support Caddy, but you can still find community support for it within the discord.
In your Caddyfile, inset the following instructions. Note that ``<>`` denotes a required option, and ``[]`` is optional to have in your config.
```Caddyfile
<myshark.ey>
reverse_proxy [ip]:3000
Loading