2026-07-17 21:28:29 +01:00
2026-07-17 03:42:59 +01:00
2026-07-17 20:47:37 +01:00
2026-07-17 21:28:29 +01:00

thingy!

some kind of hosting setup

setup

log into the vps, make sure it's fedora (or else 🔪)

sudo dnf install git -y
git clone https://gitlab.com/futile/thingy
./thingy/set-up-system.sh
exit
ssh <user>@<ip>
cd thingy
micro .env
docker compose up

continue with service-specific setups .....

services

specifics for everything

currently serving

  • via docker
    • caddy http server & reverse proxy
    • stalwart mailserver
    • bulwark webmail
  • via caddy
    • m.yaoi.dog mail (server & admin dash)
    • mail.yaoi.dog mail (webmail)

dns setup

type host value notes
A @ <ip> apex domain
A m <ip> mailserver
A mail <ip> webmail
CAA @ 0 issue "letsencrypt.org" allow caddy to issue certs

stalwart

first setup

  • server identity
    • server hostname: m.yaoi.dog
    • default email domain: yaoi.dog
    • automatically obtain tls certificate: true
    • generate email signing keys: true
  • storage
    • main data storage: rocksdb
    • path: /var/lib/stalwart/
  • account directory
    • directory type: use internal
  • logging
    • log destination: console
  • automatic dns management
    • dns server type: porkbun
    • description: porkbun

further setup

  • settings -> security -> allowed ips
    • added 172.18.0.0/24; reason: internal
  • settings -> network -> http -> security
    • permissive cors policy: true [restart needed]

notes

  • in docker-compose.yml, a stalwart-logs volume is currently defined but not being used, due to the fact that stalwart does not seem to create anything within it. i need to figure out why. for now, stalwart logs to console.

useful links

bulwark

useful links

S
Description
No description provided
Readme
69 KiB
Languages
Shell 100%