Daily Post December 16 2025: Difference between revisions
| Line 27: | Line 27: | ||
Required software includes a reverse proxy like Nginx or Apache for handling HTTPS traffic on ports 80/443 and proxying to Synapse's ports (8008 for client-server, 8448 for federation), plus SSL certificates from Let's Encrypt. | Required software includes a reverse proxy like Nginx or Apache for handling HTTPS traffic on ports 80/443 and proxying to Synapse's ports (8008 for client-server, 8448 for federation), plus SSL certificates from Let's Encrypt. | ||
So...Install Synapse via Debian packages, pip, or Docker, generate a signing key, and then configure a '''homeserver.yaml''' with a domain, then for a database use '''SQLite''' for small setups or maybe '''PostgreSQL''' for scale, and finally configure '''TURN''' server settings for VoIP using '''Coturn''' | So...Install Synapse via Debian packages, pip, or Docker, generate a signing key, and then configure a '''homeserver.yaml''' with a domain, then for a database use '''SQLite''' for small setups or maybe '''PostgreSQL''' for scale, and finally configure the '''TURN''' server settings for VoIP using '''Coturn''' | ||
For a client like '''Element''', serve it via another subdomain with a custom config.json pointing to your homeserver. Federation with other matrix servers requires proper delegation headers in the proxy config; non-federated setups simplify port exposure. Ongoing maintenance involves backups, updates, and monitoring storage growth from media and logs | For a client like '''Element''', serve it via another subdomain with a custom config.json pointing to your homeserver. Federation with other matrix servers requires proper delegation headers in the proxy config; non-federated setups simplify port exposure. Ongoing maintenance involves backups, updates, and monitoring storage growth from media and logs | ||