Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,28 @@ make down
make help # View all available commands
```

The preferred way to configure the shared footer behavior is directly in the
WordPress theme via:

- `Appearance > Customize > Footer integration`

There you configure the webhook secret and optional allowlist used by WordPress
to receive the footer artifacts pushed by the static site build.

On the static-site build side, the webhook publisher is configured with runtime
environment variables.

Priority order is:

1. theme configuration (`Appearance > Customize > Footer integration`)
2. runtime environment variables for the site build webhook
3. existing locally stored footer artifact in WordPress

The site build webhook expects:

- `LIBRESIGN_FOOTER_WEBHOOK_URL`
- `LIBRESIGN_FOOTER_WEBHOOK_SECRET`

You can pass component names after `make up` to start only part of the local
stack:

Expand Down
2 changes: 1 addition & 1 deletion wordpress-docker