<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Servers and Services on OpenBSD Handbook</title><link>https://www.openbsdhandbook.com/howto/services/</link><description>Recent content in Servers and Services on OpenBSD Handbook</description><generator>Hugo</generator><language>en</language><atom:link href="https://www.openbsdhandbook.com/howto/services/index.xml" rel="self" type="application/rss+xml"/><item><title>Set Up WordPress on OpenBSD</title><link>https://www.openbsdhandbook.com/wordpress/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.openbsdhandbook.com/wordpress/</guid><description>&lt;h2 id="synopsis"&gt;
 Synopsis
 &lt;a class="anchor" href="#synopsis"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Deploy WordPress on OpenBSD with the base web server &lt;a href="https://man.openbsdhandbook.com/man.cgi?page=httpd&amp;amp;section=8" target="_blank" rel="noopener noreferrer"&gt;httpd(8)&lt;/a&gt;

, PHP-FPM from packages, and MariaDB from packages. OpenBSD runs the web server in a &lt;a href="https://man.openbsdhandbook.com/man.cgi?page=chroot&amp;amp;section=2" target="_blank" rel="noopener noreferrer"&gt;chroot(2)&lt;/a&gt;

 at &lt;code&gt;/var/www&lt;/code&gt;, so name resolution and interprocess communication must work from within that environment.&lt;/p&gt;
&lt;p&gt;Privileged commands use &lt;code&gt;doas&lt;/code&gt;; &lt;a href="https://www.openbsdhandbook.com/admin-account"&gt;configure administrative access&lt;/a&gt;

 first.&lt;/p&gt;
&lt;h2 id="preparation-name-resolution-in-the-httpd-chroot"&gt;
 Preparation: Name Resolution in the httpd Chroot
 &lt;a class="anchor" href="#preparation-name-resolution-in-the-httpd-chroot"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Ensure that processes running inside &lt;code&gt;/var/www&lt;/code&gt; can resolve hostnames. Create the chroot’s &lt;code&gt;/etc&lt;/code&gt; and provide resolver configuration per &lt;a href="https://man.openbsdhandbook.com/man.cgi?page=resolv.conf&amp;amp;section=5" target="_blank" rel="noopener noreferrer"&gt;resolv.conf(5)&lt;/a&gt;

. Optionally create &lt;code&gt;/etc/hosts&lt;/code&gt; entries per &lt;a href="https://man.openbsdhandbook.com/man.cgi?page=hosts&amp;amp;section=5" target="_blank" rel="noopener noreferrer"&gt;hosts(5)&lt;/a&gt;

.&lt;/p&gt;</description></item><item><title>Build a Mail Server with OpenSMTPD, Dovecot, and Rspamd</title><link>https://www.openbsdhandbook.com/mail-server/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.openbsdhandbook.com/mail-server/</guid><description>&lt;h2 id="synopsis"&gt;
 Synopsis
 &lt;a class="anchor" href="#synopsis"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;This guide combines the base-system &lt;a href="https://man.openbsdhandbook.com/man.cgi?page=smtpd&amp;amp;section=8" target="_blank" rel="noopener noreferrer"&gt;smtpd(8)&lt;/a&gt;

 service, packaged Dovecot IMAP and LMTP delivery, and packaged Rspamd filtering into one small mail server. It uses system accounts and Maildir storage to keep the initial design reviewable.&lt;/p&gt;
&lt;p&gt;An Internet mail server is an operational commitment. Correct DNS, abuse handling, TLS renewal, filtering, queue monitoring, backups, reputation, and timely upgrades are part of the service. Test the complete design on a non-production domain before changing live MX records.&lt;/p&gt;</description></item></channel></rss>