Skip to content

Changes from v3.1.0 to v3.2.0#269

Merged
apata merged 4 commits intov3.2.0from
v3.2.0-proposal
Jan 26, 2026
Merged

Changes from v3.1.0 to v3.2.0#269
apata merged 4 commits intov3.2.0from
v3.2.0-proposal

Conversation

@apata
Copy link
Contributor

@apata apata commented Jan 16, 2026

@apata apata marked this pull request as ready for review January 16, 2026 10:53
@apata apata merged commit f602706 into v3.2.0 Jan 26, 2026
@zoldar
Copy link

zoldar commented Jan 26, 2026

It's a bit outside the scope, but I've tried to go through the instructions on a fresh machine (VM) and I've stumbled on some issues:


$ touch .env
$ echo "BASE_URL=https://plausible.example.com" >> .env
$ echo "SECRET_KEY_BASE=$(openssl rand -base64 48)" >> .env

$ cat .env
BASE_URL=https://plausible.example.com
SECRET_KEY_BASE=As0fZsJlUpuFYSthRjT5Yflg/NlxkFKPRro72xMLXF8yInZ60s6xGGXYVqml+XN1

I know it's an example, but I'd replace the secret key string with ellipsis, just in case 🙈


---

There's a missing indent in the override example. Instead of:

```bash
$ echo "HTTP_PORT=80" >> .env
$ echo "HTTPS_PORT=443" >> .env

$ cat > compose.override.yml << EOF
services:
    plausible:
    ports:
        - 80:80
        - 443:443
EOF

it should be:


```bash
$ echo "HTTP_PORT=80" >> .env
$ echo "HTTPS_PORT=443" >> .env

$ cat > compose.override.yml << EOF
services:
    plausible:
        ports:
            - 80:80
            - 443:443
EOF

Perhaps it would make sense to reformat/split snippets (with output examples in separate code blocks) so that they can be copied with a single click instead of selecting manually?


The 500 template shows "We have been notified" 😅

image

@apata
Copy link
Contributor Author

apata commented Jan 26, 2026

@aerosol @zoldar Thanks for checking this!

@zoldar I applied the fixes that you mentioned
#271

Perhaps it would make sense to reformat/split snippets (with output examples in separate code blocks) so that they can be copied with a single click instead of selecting manually?

It's a good idea (there's another PR with that suggestion), and I tried to when posting this PR, but it actually made it harder to read and understand, at least for me. I'm not opposed to it if you want to give it a shot though.

@apata apata deleted the v3.2.0-proposal branch January 26, 2026 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants