Quick Start

Launch a WordPress Site in 5 Minutes

1. Create Config Directory

mkdir -p /etc/sweety

2. Write Minimal Config

/etc/sweety/sweety.toml:

[[sites]]
name        = "wordpress"
server_name = ["php.example.com"]
listen      = [80]
listen_tls  = [443]
root        = "/var/www/wordpress"
preset      = "wordpress"
php_fastcgi = "/run/php/php8.2-fpm.sock"

These 7 lines are equivalent to 50+ lines of Nginx config, automatically providing:

• HTTP → HTTPS 301 redirect (force_https enabled by default, no explicit config needed)
• Let's Encrypt automatic certificate issuance and renewal (no email required)
• Optimal WordPress location routing rules (static files served directly, PHP forwarding, security filtering)
• HTTP/1.1 + HTTP/2 + HTTP/3 full protocol support

💡 force_https defaults to true. To allow plain HTTP access, explicitly set force_https = false.

3. Validate Config

sweety validate -c /etc/sweety/sweety.toml

4. Start

# Foreground (for debugging)
sweety run -c /etc/sweety/sweety.toml

# Background
sweety start -c /etc/sweety/sweety.toml

---

Launch a Static Site in 5 Minutes

[[sites]]
name        = "blog"
server_name = ["blog.example.com"]
listen      = [80]
listen_tls  = [443]
root        = "/var/www/blog"
preset      = "static"

---

Configure a Reverse Proxy in 5 Minutes

[[sites]]
name        = "api"
server_name = ["api.example.com"]
listen      = [80]
listen_tls  = [443]

[[sites.upstreams]]
name  = "backend"
nodes = [
    { addr = "127.0.0.1:3000", weight = 1 }
]

[[sites.locations]]
path    = "/"
handler = "proxy"
upstream = "backend"

---

Multi-Site Example

[[sites]]
name        = "site1"
server_name = ["site1.example.com"]
listen      = [80]
listen_tls  = [443]
root        = "/var/www/site1"
preset      = "static"

[[sites]]
name        = "site2"
server_name = ["site2.example.com"]
listen      = [80]
listen_tls  = [443]
root        = "/var/www/wordpress"
preset      = "wordpress"
php_fastcgi = "/run/php/php8.2-fpm.sock"

Multiple sites share the same port — Sweety automatically routes via SNI (TLS) and Host header (HTTP).