#ORLY?🦉 #devstr #progressreport
v0.48.13 has some small but important fixes with the event view in the web UI that were not loading entries already in cache properly. there is a toggle to disable blossom, like now set up on https://archive.orly.dev wss://archive.orly.dev/ because it's a read only aggregator.
btw, both relay.orly.dev and archive.orly.dev are single application deployments on their VPSs, using the letsencrypt certificiate jazz, so if you use it this way instead of behind a reverse proxy, make sure you
/usr/sbin/setcap cap_net_bind_service=+ep
this allows it permission to listen to port 80 and 443 for http/https
v0.48.13 has some small but important fixes with the event view in the web UI that were not loading entries already in cache properly. there is a toggle to disable blossom, like now set up on https://archive.orly.dev wss://archive.orly.dev/ because it's a read only aggregator.
btw, both relay.orly.dev and archive.orly.dev are single application deployments on their VPSs, using the letsencrypt certificiate jazz, so if you use it this way instead of behind a reverse proxy, make sure you
/usr/sbin/setcap cap_net_bind_service=+ep
this allows it permission to listen to port 80 and 443 for http/https