silentmode/sirius-press
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
sirius-press/docker/Dockerfile

78 lines
3 KiB
Text
Raw Permalink Normal View History

build(sirius-press): build from the vendored subtree instead of a download The subtree is in place, so everything that used to fetch and patch core at build time now just copies it. tools/build.sh copies wordpress/ — no download, no checksum step, because there is nothing to fetch and nothing to trust that is not already in the repository docker/Dockerfile COPY wordpress/ instead of curl + sha256 + patch; the build args and the `patch` package are gone docker-compose.yml no WP_VERSION / WP_URL / WP_SHA256 to keep in step tools/update-wordpress.sh is rewritten around what the subtree makes possible. It imports the pristine release onto sirius-press/wordpress-upstream and then `git subtree merge`s that branch, which three-way merges upstream against the fork's own commit. A patch either applies with fuzz and hopes or fails and leaves you re-deriving the change by hand; a merge conflict is resolved once, in the file, and the next release merges against the resolution. patches/ survives as documentation rather than mechanism, and is now generated: tools/refresh-patches.sh diffs the subtree against the pristine import and rewrites the directory, with --check for CI. It answers the question anyone auditing a fork asks first — what exactly did you change inside WordPress? — in a minute, which `git log wordpress/` cannot, because that log is mostly upstream imports. Generated documentation stays true; a hand-maintained record of a core diff drifts, and a stale one is worse than none because people trust it. One test change worth noting: the syntax sweep no longer walks all of wordpress/. It lints the fork's own PHP plus every core file patches/ says the fork touches, which keeps the suite at seven seconds instead of a minute while still covering the only core file that can break.
2026-09-21 03:19:28 +02:00
# Sirius Press — PHP-FPM image with the patched WordPress baked in.
feat(sirius-press): a WordPress where the account is a key, not a mailbox WordPress makes two assumptions this project cannot accept: that identity comes from an email address, and that a site lives at one server. Both are things somebody else can take away — a mailbox is rented from a provider who can close it or be compelled to open it, and a server is one seizure from being gone. Sirius Press replaces the first and hedges the second. Signing in means signing a challenge with the key that controls a CashAddress. The address is recovered from the signature, so nothing is typed but the signature itself, and the result is an ordinary WordPress session cookie — roles, capabilities, nonces and the REST API never learn the login was different. Three ways to produce one: a wallet the browser already exposes, a phrase used once in the page and wiped, or a signature pasted in from any BIP-137 wallet, which needs no JavaScript and lets the key stay on a machine that never touches the web. There is no password reset, and the recovery page says so plainly rather than offering a form that cannot work. A reset mechanism is by construction a way to take an account from its owner, and it is always easier to attack than the cryptography it bypasses. Publishing a post also exports it as static HTML to the name's storage on Sia, signed by the key that owns the name, so the site keeps answering when the server does not. Email as a feature is untouched. wp_mail() still works, SMTP still sends, and contact forms still deliver to addresses real people typed. Only mail to the site's own unroutable placeholder addresses is diverted to an in-app inbox. The objection was to email as identity, not to email. Core is pinned and patched rather than vendored. WordPress 7.1.1 is 149 MB and 5,008 files; the fork's entire core diff is 75 lines in wp-admin/install.php. Carrying the former to express the latter would bury the patch where nobody reviews it and make every clone of the monorepo pay for it. Upstream releases still merge through tools/update-wordpress.sh, which reapplies the series and says exactly which hunk needs a human. The cryptography is implemented twice — PHP on the server, JavaScript in the page — because the server must verify and the browser must sign. Both are pinned against libauth, the library the Sirius portal wallet and the BNS gateway already use, so a disagreement of one byte fails the test suite rather than presenting as a rejected login at three in the morning. 132 checks, no framework, about a second.
2026-09-21 01:39:38 +02:00
#
build(sirius-press): build from the vendored subtree instead of a download The subtree is in place, so everything that used to fetch and patch core at build time now just copies it. tools/build.sh copies wordpress/ — no download, no checksum step, because there is nothing to fetch and nothing to trust that is not already in the repository docker/Dockerfile COPY wordpress/ instead of curl + sha256 + patch; the build args and the `patch` package are gone docker-compose.yml no WP_VERSION / WP_URL / WP_SHA256 to keep in step tools/update-wordpress.sh is rewritten around what the subtree makes possible. It imports the pristine release onto sirius-press/wordpress-upstream and then `git subtree merge`s that branch, which three-way merges upstream against the fork's own commit. A patch either applies with fuzz and hopes or fails and leaves you re-deriving the change by hand; a merge conflict is resolved once, in the file, and the next release merges against the resolution. patches/ survives as documentation rather than mechanism, and is now generated: tools/refresh-patches.sh diffs the subtree against the pristine import and rewrites the directory, with --check for CI. It answers the question anyone auditing a fork asks first — what exactly did you change inside WordPress? — in a minute, which `git log wordpress/` cannot, because that log is mostly upstream imports. Generated documentation stays true; a hand-maintained record of a core diff drifts, and a stale one is worse than none because people trust it. One test change worth noting: the syntax sweep no longer walks all of wordpress/. It lints the fork's own PHP plus every core file patches/ says the fork touches, which keeps the suite at seven seconds instead of a minute while still covering the only core file that can break.
2026-09-21 03:19:28 +02:00
# Core comes from this repository's `wordpress/` subtree, not from a download
# and not from the official `wordpress` image. That image ships whatever
# version it was tagged with, and the fork's core patch is pinned to an exact
# one; applying a fork's patch to a different core is how a setup wizard ends
# up half rewritten. Copying the vendored tree makes the image contain exactly
# what `git log wordpress/` describes, with nothing fetched at build time.
feat(sirius-press): a WordPress where the account is a key, not a mailbox WordPress makes two assumptions this project cannot accept: that identity comes from an email address, and that a site lives at one server. Both are things somebody else can take away — a mailbox is rented from a provider who can close it or be compelled to open it, and a server is one seizure from being gone. Sirius Press replaces the first and hedges the second. Signing in means signing a challenge with the key that controls a CashAddress. The address is recovered from the signature, so nothing is typed but the signature itself, and the result is an ordinary WordPress session cookie — roles, capabilities, nonces and the REST API never learn the login was different. Three ways to produce one: a wallet the browser already exposes, a phrase used once in the page and wiped, or a signature pasted in from any BIP-137 wallet, which needs no JavaScript and lets the key stay on a machine that never touches the web. There is no password reset, and the recovery page says so plainly rather than offering a form that cannot work. A reset mechanism is by construction a way to take an account from its owner, and it is always easier to attack than the cryptography it bypasses. Publishing a post also exports it as static HTML to the name's storage on Sia, signed by the key that owns the name, so the site keeps answering when the server does not. Email as a feature is untouched. wp_mail() still works, SMTP still sends, and contact forms still deliver to addresses real people typed. Only mail to the site's own unroutable placeholder addresses is diverted to an in-app inbox. The objection was to email as identity, not to email. Core is pinned and patched rather than vendored. WordPress 7.1.1 is 149 MB and 5,008 files; the fork's entire core diff is 75 lines in wp-admin/install.php. Carrying the former to express the latter would bury the patch where nobody reviews it and make every clone of the monorepo pay for it. Upstream releases still merge through tools/update-wordpress.sh, which reapplies the series and says exactly which hunk needs a human. The cryptography is implemented twice — PHP on the server, JavaScript in the page — because the server must verify and the browser must sign. Both are pinned against libauth, the library the Sirius portal wallet and the BNS gateway already use, so a disagreement of one byte fails the test suite rather than presenting as a rejected login at three in the morning. 132 checks, no framework, about a second.
2026-09-21 01:39:38 +02:00
#
build(sirius-press): build from the vendored subtree instead of a download The subtree is in place, so everything that used to fetch and patch core at build time now just copies it. tools/build.sh copies wordpress/ — no download, no checksum step, because there is nothing to fetch and nothing to trust that is not already in the repository docker/Dockerfile COPY wordpress/ instead of curl + sha256 + patch; the build args and the `patch` package are gone docker-compose.yml no WP_VERSION / WP_URL / WP_SHA256 to keep in step tools/update-wordpress.sh is rewritten around what the subtree makes possible. It imports the pristine release onto sirius-press/wordpress-upstream and then `git subtree merge`s that branch, which three-way merges upstream against the fork's own commit. A patch either applies with fuzz and hopes or fails and leaves you re-deriving the change by hand; a merge conflict is resolved once, in the file, and the next release merges against the resolution. patches/ survives as documentation rather than mechanism, and is now generated: tools/refresh-patches.sh diffs the subtree against the pristine import and rewrites the directory, with --check for CI. It answers the question anyone auditing a fork asks first — what exactly did you change inside WordPress? — in a minute, which `git log wordpress/` cannot, because that log is mostly upstream imports. Generated documentation stays true; a hand-maintained record of a core diff drifts, and a stale one is worse than none because people trust it. One test change worth noting: the syntax sweep no longer walks all of wordpress/. It lints the fork's own PHP plus every core file patches/ says the fork touches, which keeps the suite at seven seconds instead of a minute while still covering the only core file that can break.
2026-09-21 03:19:28 +02:00
# Core is staged at /opt/sirius-press/core, not at the document root. The
feat(sirius-press): a WordPress where the account is a key, not a mailbox WordPress makes two assumptions this project cannot accept: that identity comes from an email address, and that a site lives at one server. Both are things somebody else can take away — a mailbox is rented from a provider who can close it or be compelled to open it, and a server is one seizure from being gone. Sirius Press replaces the first and hedges the second. Signing in means signing a challenge with the key that controls a CashAddress. The address is recovered from the signature, so nothing is typed but the signature itself, and the result is an ordinary WordPress session cookie — roles, capabilities, nonces and the REST API never learn the login was different. Three ways to produce one: a wallet the browser already exposes, a phrase used once in the page and wiped, or a signature pasted in from any BIP-137 wallet, which needs no JavaScript and lets the key stay on a machine that never touches the web. There is no password reset, and the recovery page says so plainly rather than offering a form that cannot work. A reset mechanism is by construction a way to take an account from its owner, and it is always easier to attack than the cryptography it bypasses. Publishing a post also exports it as static HTML to the name's storage on Sia, signed by the key that owns the name, so the site keeps answering when the server does not. Email as a feature is untouched. wp_mail() still works, SMTP still sends, and contact forms still deliver to addresses real people typed. Only mail to the site's own unroutable placeholder addresses is diverted to an in-app inbox. The objection was to email as identity, not to email. Core is pinned and patched rather than vendored. WordPress 7.1.1 is 149 MB and 5,008 files; the fork's entire core diff is 75 lines in wp-admin/install.php. Carrying the former to express the latter would bury the patch where nobody reviews it and make every clone of the monorepo pay for it. Upstream releases still merge through tools/update-wordpress.sh, which reapplies the series and says exactly which hunk needs a human. The cryptography is implemented twice — PHP on the server, JavaScript in the page — because the server must verify and the browser must sign. Both are pinned against libauth, the library the Sirius portal wallet and the BNS gateway already use, so a disagreement of one byte fails the test suite rather than presenting as a rejected login at three in the morning. 132 checks, no framework, about a second.
2026-09-21 01:39:38 +02:00
# entrypoint copies it into place on every start, which is what makes
# `docker compose build --pull && up -d` a real upgrade: the usual layout,
# where the document root is itself a volume, pins core to whatever version
# first created that volume and turns every security release into a manual
# migration.
#
# GMP is installed because the wallet cryptography runs in PHP. Without it the
# fork falls back to BCMath, which works and is roughly twenty times slower —
# unavoidable on a shared host, wasteful in a container we control.
FROM php:8.3-fpm-bookworm
RUN set -eux; \
apt-get update; \
apt-get install -y --no-install-recommends \
build(sirius-press): build from the vendored subtree instead of a download The subtree is in place, so everything that used to fetch and patch core at build time now just copies it. tools/build.sh copies wordpress/ — no download, no checksum step, because there is nothing to fetch and nothing to trust that is not already in the repository docker/Dockerfile COPY wordpress/ instead of curl + sha256 + patch; the build args and the `patch` package are gone docker-compose.yml no WP_VERSION / WP_URL / WP_SHA256 to keep in step tools/update-wordpress.sh is rewritten around what the subtree makes possible. It imports the pristine release onto sirius-press/wordpress-upstream and then `git subtree merge`s that branch, which three-way merges upstream against the fork's own commit. A patch either applies with fuzz and hopes or fails and leaves you re-deriving the change by hand; a merge conflict is resolved once, in the file, and the next release merges against the resolution. patches/ survives as documentation rather than mechanism, and is now generated: tools/refresh-patches.sh diffs the subtree against the pristine import and rewrites the directory, with --check for CI. It answers the question anyone auditing a fork asks first — what exactly did you change inside WordPress? — in a minute, which `git log wordpress/` cannot, because that log is mostly upstream imports. Generated documentation stays true; a hand-maintained record of a core diff drifts, and a stale one is worse than none because people trust it. One test change worth noting: the syntax sweep no longer walks all of wordpress/. It lints the fork's own PHP plus every core file patches/ says the fork touches, which keeps the suite at seven seconds instead of a minute while still covering the only core file that can break.
2026-09-21 03:19:28 +02:00
ca-certificates curl \
feat(sirius-press): a WordPress where the account is a key, not a mailbox WordPress makes two assumptions this project cannot accept: that identity comes from an email address, and that a site lives at one server. Both are things somebody else can take away — a mailbox is rented from a provider who can close it or be compelled to open it, and a server is one seizure from being gone. Sirius Press replaces the first and hedges the second. Signing in means signing a challenge with the key that controls a CashAddress. The address is recovered from the signature, so nothing is typed but the signature itself, and the result is an ordinary WordPress session cookie — roles, capabilities, nonces and the REST API never learn the login was different. Three ways to produce one: a wallet the browser already exposes, a phrase used once in the page and wiped, or a signature pasted in from any BIP-137 wallet, which needs no JavaScript and lets the key stay on a machine that never touches the web. There is no password reset, and the recovery page says so plainly rather than offering a form that cannot work. A reset mechanism is by construction a way to take an account from its owner, and it is always easier to attack than the cryptography it bypasses. Publishing a post also exports it as static HTML to the name's storage on Sia, signed by the key that owns the name, so the site keeps answering when the server does not. Email as a feature is untouched. wp_mail() still works, SMTP still sends, and contact forms still deliver to addresses real people typed. Only mail to the site's own unroutable placeholder addresses is diverted to an in-app inbox. The objection was to email as identity, not to email. Core is pinned and patched rather than vendored. WordPress 7.1.1 is 149 MB and 5,008 files; the fork's entire core diff is 75 lines in wp-admin/install.php. Carrying the former to express the latter would bury the patch where nobody reviews it and make every clone of the monorepo pay for it. Upstream releases still merge through tools/update-wordpress.sh, which reapplies the series and says exactly which hunk needs a human. The cryptography is implemented twice — PHP on the server, JavaScript in the page — because the server must verify and the browser must sign. Both are pinned against libauth, the library the Sirius portal wallet and the BNS gateway already use, so a disagreement of one byte fails the test suite rather than presenting as a rejected login at three in the morning. 132 checks, no framework, about a second.
2026-09-21 01:39:38 +02:00
libfreetype6-dev libjpeg62-turbo-dev libpng-dev libwebp-dev \
libzip-dev libgmp-dev libicu-dev \
; \
docker-php-ext-configure gd --with-freetype --with-jpeg --with-webp; \
docker-php-ext-install -j"$(nproc)" \
bcmath gd gmp intl mysqli opcache zip exif \
; \
rm -rf /var/lib/apt/lists/*
# Settings a WordPress host wants and the PHP image does not set.
RUN { \
echo 'upload_max_filesize = 64M'; \
echo 'post_max_size = 64M'; \
echo 'memory_limit = 256M'; \
echo 'max_execution_time = 120'; \
echo 'opcache.memory_consumption = 128'; \
echo 'opcache.max_accelerated_files = 10000'; \
echo 'opcache.revalidate_freq = 2'; \
echo 'expose_php = Off'; \
} > /usr/local/etc/php/conf.d/sirius-press.ini
build(sirius-press): build from the vendored subtree instead of a download The subtree is in place, so everything that used to fetch and patch core at build time now just copies it. tools/build.sh copies wordpress/ — no download, no checksum step, because there is nothing to fetch and nothing to trust that is not already in the repository docker/Dockerfile COPY wordpress/ instead of curl + sha256 + patch; the build args and the `patch` package are gone docker-compose.yml no WP_VERSION / WP_URL / WP_SHA256 to keep in step tools/update-wordpress.sh is rewritten around what the subtree makes possible. It imports the pristine release onto sirius-press/wordpress-upstream and then `git subtree merge`s that branch, which three-way merges upstream against the fork's own commit. A patch either applies with fuzz and hopes or fails and leaves you re-deriving the change by hand; a merge conflict is resolved once, in the file, and the next release merges against the resolution. patches/ survives as documentation rather than mechanism, and is now generated: tools/refresh-patches.sh diffs the subtree against the pristine import and rewrites the directory, with --check for CI. It answers the question anyone auditing a fork asks first — what exactly did you change inside WordPress? — in a minute, which `git log wordpress/` cannot, because that log is mostly upstream imports. Generated documentation stays true; a hand-maintained record of a core diff drifts, and a stale one is worse than none because people trust it. One test change worth noting: the syntax sweep no longer walks all of wordpress/. It lints the fork's own PHP plus every core file patches/ says the fork touches, which keeps the suite at seven seconds instead of a minute while still covering the only core file that can break.
2026-09-21 03:19:28 +02:00
# --- core, from the subtree --------------------------------------------------
COPY wordpress/ /opt/sirius-press/core/
feat(sirius-press): a WordPress where the account is a key, not a mailbox WordPress makes two assumptions this project cannot accept: that identity comes from an email address, and that a site lives at one server. Both are things somebody else can take away — a mailbox is rented from a provider who can close it or be compelled to open it, and a server is one seizure from being gone. Sirius Press replaces the first and hedges the second. Signing in means signing a challenge with the key that controls a CashAddress. The address is recovered from the signature, so nothing is typed but the signature itself, and the result is an ordinary WordPress session cookie — roles, capabilities, nonces and the REST API never learn the login was different. Three ways to produce one: a wallet the browser already exposes, a phrase used once in the page and wiped, or a signature pasted in from any BIP-137 wallet, which needs no JavaScript and lets the key stay on a machine that never touches the web. There is no password reset, and the recovery page says so plainly rather than offering a form that cannot work. A reset mechanism is by construction a way to take an account from its owner, and it is always easier to attack than the cryptography it bypasses. Publishing a post also exports it as static HTML to the name's storage on Sia, signed by the key that owns the name, so the site keeps answering when the server does not. Email as a feature is untouched. wp_mail() still works, SMTP still sends, and contact forms still deliver to addresses real people typed. Only mail to the site's own unroutable placeholder addresses is diverted to an in-app inbox. The objection was to email as identity, not to email. Core is pinned and patched rather than vendored. WordPress 7.1.1 is 149 MB and 5,008 files; the fork's entire core diff is 75 lines in wp-admin/install.php. Carrying the former to express the latter would bury the patch where nobody reviews it and make every clone of the monorepo pay for it. Upstream releases still merge through tools/update-wordpress.sh, which reapplies the series and says exactly which hunk needs a human. The cryptography is implemented twice — PHP on the server, JavaScript in the page — because the server must verify and the browser must sign. Both are pinned against libauth, the library the Sirius portal wallet and the BNS gateway already use, so a disagreement of one byte fails the test suite rather than presenting as a rejected login at three in the morning. 132 checks, no framework, about a second.
2026-09-21 01:39:38 +02:00
RUN set -eux; \
build(sirius-press): build from the vendored subtree instead of a download The subtree is in place, so everything that used to fetch and patch core at build time now just copies it. tools/build.sh copies wordpress/ — no download, no checksum step, because there is nothing to fetch and nothing to trust that is not already in the repository docker/Dockerfile COPY wordpress/ instead of curl + sha256 + patch; the build args and the `patch` package are gone docker-compose.yml no WP_VERSION / WP_URL / WP_SHA256 to keep in step tools/update-wordpress.sh is rewritten around what the subtree makes possible. It imports the pristine release onto sirius-press/wordpress-upstream and then `git subtree merge`s that branch, which three-way merges upstream against the fork's own commit. A patch either applies with fuzz and hopes or fails and leaves you re-deriving the change by hand; a merge conflict is resolved once, in the file, and the next release merges against the resolution. patches/ survives as documentation rather than mechanism, and is now generated: tools/refresh-patches.sh diffs the subtree against the pristine import and rewrites the directory, with --check for CI. It answers the question anyone auditing a fork asks first — what exactly did you change inside WordPress? — in a minute, which `git log wordpress/` cannot, because that log is mostly upstream imports. Generated documentation stays true; a hand-maintained record of a core diff drifts, and a stale one is worse than none because people trust it. One test change worth noting: the syntax sweep no longer walks all of wordpress/. It lints the fork's own PHP plus every core file patches/ says the fork touches, which keeps the suite at seven seconds instead of a minute while still covering the only core file that can break.
2026-09-21 03:19:28 +02:00
test -f /opt/sirius-press/core/wp-includes/version.php; \
sed -n "s/.*wp_version = '\\(.*\\)'.*/\\1/p" \
/opt/sirius-press/core/wp-includes/version.php \
> /opt/sirius-press/core/.sirius-core-version; \
echo "vendored WordPress $(cat /opt/sirius-press/core/.sirius-core-version)"
feat(sirius-press): a WordPress where the account is a key, not a mailbox WordPress makes two assumptions this project cannot accept: that identity comes from an email address, and that a site lives at one server. Both are things somebody else can take away — a mailbox is rented from a provider who can close it or be compelled to open it, and a server is one seizure from being gone. Sirius Press replaces the first and hedges the second. Signing in means signing a challenge with the key that controls a CashAddress. The address is recovered from the signature, so nothing is typed but the signature itself, and the result is an ordinary WordPress session cookie — roles, capabilities, nonces and the REST API never learn the login was different. Three ways to produce one: a wallet the browser already exposes, a phrase used once in the page and wiped, or a signature pasted in from any BIP-137 wallet, which needs no JavaScript and lets the key stay on a machine that never touches the web. There is no password reset, and the recovery page says so plainly rather than offering a form that cannot work. A reset mechanism is by construction a way to take an account from its owner, and it is always easier to attack than the cryptography it bypasses. Publishing a post also exports it as static HTML to the name's storage on Sia, signed by the key that owns the name, so the site keeps answering when the server does not. Email as a feature is untouched. wp_mail() still works, SMTP still sends, and contact forms still deliver to addresses real people typed. Only mail to the site's own unroutable placeholder addresses is diverted to an in-app inbox. The objection was to email as identity, not to email. Core is pinned and patched rather than vendored. WordPress 7.1.1 is 149 MB and 5,008 files; the fork's entire core diff is 75 lines in wp-admin/install.php. Carrying the former to express the latter would bury the patch where nobody reviews it and make every clone of the monorepo pay for it. Upstream releases still merge through tools/update-wordpress.sh, which reapplies the series and says exactly which hunk needs a human. The cryptography is implemented twice — PHP on the server, JavaScript in the page — because the server must verify and the browser must sign. Both are pinned against libauth, the library the Sirius portal wallet and the BNS gateway already use, so a disagreement of one byte fails the test suite rather than presenting as a rejected login at three in the morning. 132 checks, no framework, about a second.
2026-09-21 01:39:38 +02:00
# --- the fork -----------------------------------------------------------------
build(sirius-press): build from the vendored subtree instead of a download The subtree is in place, so everything that used to fetch and patch core at build time now just copies it. tools/build.sh copies wordpress/ — no download, no checksum step, because there is nothing to fetch and nothing to trust that is not already in the repository docker/Dockerfile COPY wordpress/ instead of curl + sha256 + patch; the build args and the `patch` package are gone docker-compose.yml no WP_VERSION / WP_URL / WP_SHA256 to keep in step tools/update-wordpress.sh is rewritten around what the subtree makes possible. It imports the pristine release onto sirius-press/wordpress-upstream and then `git subtree merge`s that branch, which three-way merges upstream against the fork's own commit. A patch either applies with fuzz and hopes or fails and leaves you re-deriving the change by hand; a merge conflict is resolved once, in the file, and the next release merges against the resolution. patches/ survives as documentation rather than mechanism, and is now generated: tools/refresh-patches.sh diffs the subtree against the pristine import and rewrites the directory, with --check for CI. It answers the question anyone auditing a fork asks first — what exactly did you change inside WordPress? — in a minute, which `git log wordpress/` cannot, because that log is mostly upstream imports. Generated documentation stays true; a hand-maintained record of a core diff drifts, and a stale one is worse than none because people trust it. One test change worth noting: the syntax sweep no longer walks all of wordpress/. It lints the fork's own PHP plus every core file patches/ says the fork touches, which keeps the suite at seven seconds instead of a minute while still covering the only core file that can break.
2026-09-21 03:19:28 +02:00
#
# The patch is already applied in the subtree, so there is nothing to patch
# here. patches/ is carried for auditing, not for building.
feat(sirius-press): a WordPress where the account is a key, not a mailbox WordPress makes two assumptions this project cannot accept: that identity comes from an email address, and that a site lives at one server. Both are things somebody else can take away — a mailbox is rented from a provider who can close it or be compelled to open it, and a server is one seizure from being gone. Sirius Press replaces the first and hedges the second. Signing in means signing a challenge with the key that controls a CashAddress. The address is recovered from the signature, so nothing is typed but the signature itself, and the result is an ordinary WordPress session cookie — roles, capabilities, nonces and the REST API never learn the login was different. Three ways to produce one: a wallet the browser already exposes, a phrase used once in the page and wiped, or a signature pasted in from any BIP-137 wallet, which needs no JavaScript and lets the key stay on a machine that never touches the web. There is no password reset, and the recovery page says so plainly rather than offering a form that cannot work. A reset mechanism is by construction a way to take an account from its owner, and it is always easier to attack than the cryptography it bypasses. Publishing a post also exports it as static HTML to the name's storage on Sia, signed by the key that owns the name, so the site keeps answering when the server does not. Email as a feature is untouched. wp_mail() still works, SMTP still sends, and contact forms still deliver to addresses real people typed. Only mail to the site's own unroutable placeholder addresses is diverted to an in-app inbox. The objection was to email as identity, not to email. Core is pinned and patched rather than vendored. WordPress 7.1.1 is 149 MB and 5,008 files; the fork's entire core diff is 75 lines in wp-admin/install.php. Carrying the former to express the latter would bury the patch where nobody reviews it and make every clone of the monorepo pay for it. Upstream releases still merge through tools/update-wordpress.sh, which reapplies the series and says exactly which hunk needs a human. The cryptography is implemented twice — PHP on the server, JavaScript in the page — because the server must verify and the browser must sign. Both are pinned against libauth, the library the Sirius portal wallet and the BNS gateway already use, so a disagreement of one byte fails the test suite rather than presenting as a rejected login at three in the morning. 132 checks, no framework, about a second.
2026-09-21 01:39:38 +02:00
WORKDIR /opt/sirius-press/core
COPY plugins/ /opt/sirius-press/core/wp-content/plugins/
COPY mu-plugins/ /opt/sirius-press/core/wp-content/mu-plugins/
COPY docker/entrypoint.sh /usr/local/bin/sirius-entrypoint
RUN chmod +x /usr/local/bin/sirius-entrypoint; \
mkdir -p /var/www/html /var/www/config; \
chown -R www-data:www-data /var/www/html /var/www/config
WORKDIR /var/www/html
ENTRYPOINT ["sirius-entrypoint"]
CMD ["php-fpm"]
Reference in a new issue Copy permalink