Simple, open source, lightweight (< 1 KB) and privacy-friendly web analytics alternative to Google Analytics.
AGPL-3.0 License
The highlights of this release candidate are:
As of version 2.1.0 this project will split into Plausible Community Edition and Plausible Enterprise Edition. The Community Edition (CE) will remain completely open source under the AGPLv3 license. The Enterprise Edition (EE) will contain extra features that will be published as source-available on Github, but we do not grant rights for anyone else to use, distribute or otherwise exploit these features. Read more here.
As part of this change, we are also rebranding the project. The new logos for CE and EE will be different so as to clarify which version is being referred to or used at any given time.
And finally as a contributor, you will have to sign a Contributor License Agreement (CLA) in order for you PRs to be considered for merging.
⚠️ This guide assumes you are using v2.0.0 ⚠️
Add a secret key for the new required TOTP_VAULT_KEY
environment variable
console
$ openssl rand -base64 32
aihU7k+GSBKbcVFuX9VEPyUhuwlKEomqA94/SQQ0NR4=
plausible-conf.env
BASE_URL=https://plausible.example.com
SECRET_KEY_BASE=PkVcxRgQDfQyhPETlog3vvCrj5LdYFSv4ejPEJHJO+i/37w6RZfRjeVCpJayjUjJMfXsNurcv5upPhTRoD3KgQ==
+ TOTP_VAULT_KEY=aihU7k+GSBKbcVFuX9VEPyUhuwlKEomqA94/SQQ0NR4=
This new key is used to encrypt TOTP secrets at rest.
Update the images used for plausible
and plausible_events_db
(thank you @lordcris https://github.com/plausible/analytics/discussions/3817#discussioncomment-8569053)
docker-compose.yml
plausible:
- image: plausible/analytics:v2.0.0
+ image: ghcr.io/plausible/community-edition:v2.1.0-rc.0
plausible_events_db:
- image: clickhouse/clickhouse-server:22.6-alpine
+ image: clickhouse/clickhouse-server:23.3.7.5-alpine
and restart the containers
console
$ cd hosting
$ docker compose stop plausible plausible_events_db
$ docker compose rm plausible plausible_events_db
$ docker compose up -d
This will boot up the new version of the app.
Following changes have been made since v2.0.0:
contains
/matches
operator for Sources, Browsers and Operating Systems.event:goal
propertycontains
/matches
operator for custom propertiesreferrers.csv
to CSV exportcustom_props.csv
to CSV export (almost the same as the old prop_breakdown.csv
, but has different column headers, and includes props for pageviews too, not only custom events)referrers.csv
to CSV exportCLICKHOUSE_MAX_BUFFER_SIZE_BYTES
env var which defaults to 100000
(100KB)prop_names
returned in the Stats API event:goal
breakdown responseprop-breakdown.csv
file from CSV exportCLICKHOUSE_MAX_BUFFER_SIZE
CLICKHOUSE_MAX_BUFFER_SIZE
with CLICKHOUSE_MAX_BUFFER_SIZE_BYTES
(none)
values in custom property breakdown for the first page (pagination) of resultsPublished by ruslandoga over 1 year ago
The highlights of this release are:
⚠️ ⚠️ ⚠️
Upgrading to
v2.0
requires performing a data migration.
Please read these notes until the end before deployingv2.0.0
The steps below have been tested with clickhouse/clickhouse-server:22.6-alpine
please make sure to upgrade ClickHouse to at least this version.
In your docker-compose.yml update the image used for plausible_events_db to a newer ClickHouse version:
plausible_events_db:
- image: yandex/clickhouse-server:21.3.2.5
+ image: clickhouse/clickhouse-server:22.6-alpine
$ docker compose stop plausible plausible_events_db
$ docker compose rm plausible_events_db
$ docker compose up -d
This will boot up the new version of ClickHouse.
Related PR: https://github.com/plausible/hosting/pull/45
In your docker-compose.yml
update the image used for plausible
to v2.0.0
plausible:
- image: plausible/analytics:v1.5.1
+ image: plausible/analytics:v2.0.0
and restart the container
$ cd hosting
$ docker compose stop plausible
$ docker compose rm plausible
$ docker compose up -d
This will boot up the new version of the app.
If you open the dashboards now, you wouldn't see any past metrics. This is expected as v2.0
uses the new events_v2
and sessions_v2
tables to store analytics data. We need to perform data migration to copy the data into the new tables.
⚠️ ⚠️ ⚠️
You need enough free disk space available for x2 of the current
plausible_events_db
'sevent-data
volume size. You can use something likedocker system df -v | grep hosting_event-data
to check how much space the current volume is occupying.
Connect to the running plausible
container and start the migration flow
$ cd hosting
$ docker compose exec plausible bin/plausible rpc Plausible.DataMigration.NumericIDs.run
You can attempt this migration multiple times unless you drop v1
tables.
Once you verify the migration went well, the old tables can be dropped. It's easiest to use clickhouse-client
for this
$ ch hosting
$ docker compose exec plausible_events_db clickhouse-client
:) \c plausible_events_db
:) show tables;
:) drop table events;
:) drop table sessions;
See https://clickhouse.com/docs/en/operations/server-configuration-parameters/settings#max-table-size-to-drop for how to drop tables with more than 50GB of data.
In your plausible-config.env
set MAXMIND_LICENSE_KEY
environment variable and get an automatically updated GeoLite2 City geolocation database. The database edition is configurable with MAXMIND_EDITION
environment variable and defaults to GeoLite2-City
.
- IP_GEOLOCATION_DB=...
+ MAXMIND_LICENSE_KEY=LNpsJCCKPis6XvBP
+ MAXMIND_EDITION=GeoLite2-City
Note that for the changes in plausible-config.env
to propagate to the plausible
, the container needs to be recreated:
$ docker compose stop plausible
$ docker compose rm plausible
$ docker compose up -d
Also note that using GeoLite2-City
edition requires more RAM than using GeoLite2-Country
.
Now you can remove any other volumes and services used to download, store, and update geolocation databases.
Following changes have been made since v1.5:
with_imported=true
in Stats API aggregate endpointtagged-events
classnamesBamboo.MailgunAdapter
, Bamboo.MandrillAdapter
, Bamboo.SendGridAdapter
plausible/analytics#2649PUT /api/v1/sites
)LOG_FAILED_LOGIN_ATTEMPTS
environment variable to enable failed login attempts logs plausible/analytics#2936MAILER_NAME
environment variable support plausible/analytics#2937MAILGUN_BASE_URI
support for Bamboo.MailgunAdapter
plausible/analytics#2935bounce_rate
IP_BLOCKLIST
environment variablecustom_dimension_filter
feature flag plausible/analytics#2996Published by ruslandoga over 1 year ago
The highlights of this release are:
Admin user registration is now done through the UI instead of configuration variables. At first launch, users are presented with a registration page which will create the admin account. Admin account related configuration variables are ignored going forward. See below for details.
Admin user registration is required from 1.5 onwards. We are deprecating the DISABLE_AUTH
option which allowed Plausible to be used without any user account at all.
Users with existing admin accounts are not affected, but we recommend removing the unused configuration variables. A benefit of moving admin account management to the UI is that you can now change the admin email account through the UI. Previously, this was done by manual database changes and configuration change which required restarting the service.
In your docker-compose.yml
update the image used for plausible
to v1.5.1
plausible:
- image: plausible/analytics:v1.4
+ image: plausible/analytics:v1.5.1
Please make sure to not use v1.5.0
release which had startup problems: https://github.com/plausible/analytics/issues/2491
$ docker compose stop plausible
$ docker compose rm plausible
$ docker compose up -d
This will boot up the new version of the app.
⚠️ Note that this city level geolocation feature requires extra ~1GB of RAM to work. If you don't have enough RAM available, you might experience slow container startups and restarts.
City level geolocation can be enabled by mounting a volume with the downloaded geonames.csv
and geolite2-city.mmdb
and setting GEONAMES_SOURCE_FILE
and IP_GEOLOCATION_DB
to point to them:
$ # custom (smaller) csv can be used, see https://github.com/plausible/location#cities for more info
$ curl -O https://s3.eu-central-1.wasabisys.com/plausible-application/geonames.csv
$ export MAXMIND_LICENSE_KEY=LNpsJCCKPis6XvBP # this key is not valid anymore
$ curl -L "https://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-City&license_key=${MAXMIND_LICENSE_KEY}&suffix=tar.gz" -o geolite2-city.mmdb.gz
$ gunzip geolite2-city.mmdb.gz
docker-compose.yml
plausible:
image: plausible/analytics:v1.5.1
+ volumes:
+ - ./geonames.csv:/etc/app/geonames.csv:ro
+ - ./geolite2-city.mmdb:/etc/app/geolite2-city.mmdb:ro
plausible-conf.env
BASE_URL=replace-me
SECRET_KEY_BASE=replace-me
+ GEONAMES_SOURCE_FILE=/etc/app/geonames.csv
+ IP_GEOLOCATION_DB=/etc/app/geolite2-city.mmdb
In your docker-compose.yml
update the image used for plausible_events_db
to a newer ClickHouse version:
plausible_events_db:
- image: yandex/clickhouse-server:21.3.2.5
+ image: clickhouse/clickhouse-server:22.6-alpine
$ docker compose stop plausible plausible_events_db
$ docker compose rm plausible_events_db
$ docker compose up -d
This will boot up the new version of ClickHouse.
Related PR: https://github.com/plausible/hosting/pull/45
Upgrading PostgreSQL is a bit trickier, here's the upgrade guide.
ADMIN_USER_EMAIL
, ADMIN_USER_NAME
, ADMIN_USER_PWD
, DISABLE_AUTH
environment variables are no longer supported and are ignored if set.
Please remove them from plausible-conf.env
:
- ADMIN_USER_EMAIL=replace-me
- ADMIN_USER_NAME=replace-me
- ADMIN_USER_PWD=replace-me
- DISABLE_AUTH=true
BASE_URL=replace-me
SECRET_KEY_BASE=replace-me
/entrypoint.sh db init-admin
command that was responsible for creating the admin user is also deprecated.
Please remove it from docker-compose.yml
:
plausible:
image: plausible/analytics:v1.5.1
- command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh db init-admin && /entrypoint.sh run"
+ command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh run"
Following changes have been made since v1.4
:
tagged-events
script extension for out-of-the-box custom event tracking|
characters with \
in Stats API filter valueslimit
parameter in Stats APIexclusions
script extension now also takes a data-include
attribute tagfile-downloads
script extension for automatically tracking file downloads as custom eventsPUT /api/v1/sites/goals
with form params site_id
, event_name
and/or page_path
, and goal_type
with supported types event
and page
DELETE /api/v1/sites/goals/:goal_id
with form params site_id
u
option can now be used in the manual
extension to specify a URL when triggering events.utm_content
and utm_term
plausible/analytics#515LISTEN_IP
configuration parameter plausible/analytics#1189property=event:goal
returns custom goal properties (within props
)ECTO_IPV6
)contains
, available for page
, entry_page
, exit_page
GET /api/v1/sites/:site_id
script.exclusions.hash.js
.pages.csv
file now includes pageviews again plausible/analytics#1878
script.file-downloads.outbound-links.js
only sends an outbound link event when an outbound download link is clickedentry_page
and exit_page
to be part of the Page
filter groupView all
link to the site-switcher dropdown in the dashboard.+ Add Site
link to the site-switcher dropdown in the dashboard.DISABLE_REGISTRATIONS
configuration parameter can now accept invite_only
to allow invited users to register an account while keeping regular registrations disabled plausible/analytics#1841DISABLE_AUTH
is no longer supportedPublished by ruslandoga over 1 year ago
The highlights of this release are:
⚠️ ⚠️ ⚠️
Upgrading to
v2.0
requires performing a data migration.
Please read these notes until the end before deployingv2.0.0-rc.2
The steps below have been tested with clickhouse/clickhouse-server:22.6-alpine
please make sure to upgrade ClickHouse to at least this version.
In your docker-compose.yml update the image used for plausible_events_db to a newer ClickHouse version:
plausible_events_db:
- image: yandex/clickhouse-server:21.3.2.5
+ image: clickhouse/clickhouse-server:22.6-alpine
$ docker compose stop plausible plausible_events_db
$ docker compose rm plausible_events_db
$ docker compose up -d
This will boot up the new version of ClickHouse.
Related PR: https://github.com/plausible/hosting/pull/45
In your docker-compose.yml
update the image used for plausible
to v2.0.0-rc.2
plausible:
- image: plausible/analytics:v1.5.1
+ image: plausible/analytics:v2.0.0-rc.2
and restart the container
$ cd hosting
$ docker compose stop plausible
$ docker compose rm plausible
$ docker compose up -d
This will boot up the new version of the app.
If you open the dashboards now, you wouldn't see any past metrics. This is expected as v2.0
uses the new events_v2
and sessions_v2
tables to store analytics data. We need to perform data migration to copy the data into the new tables.
⚠️ ⚠️ ⚠️
You need enough free disk space available for x2 of the current
plausible_events_db
'sevent-data
volume size. You can use something likedocker system df -v | grep hosting_event-data
to check how much space the current volume is occupying.
Connect to the running plausible
container and start the migration flow
$ cd hosting
$ docker compose exec plausible bin/plausible rpc Plausible.DataMigration.NumericIDs.run
You can attempt this migration multiple times unless you drop v1
tables.
Once you verify the migration went well, the old tables can be dropped. It's easiest to use clickhouse-client
for this
$ ch hosting
$ docker compose exec plausible_events_db clickhouse-client
:) \c plausible_events_db
:) show tables;
:) drop table events;
:) drop table sessions;
See https://clickhouse.com/docs/en/operations/server-configuration-parameters/settings#max-table-size-to-drop for how to drop tables with more than 50GB of data.
In your plausible-config.env
set MAXMIND_LICENSE_KEY
environment variable and get an automatically updated GeoLite2 City geolocation database. The database edition is configurable with MAXMIND_EDITION
environment variable and defaults to GeoLite2-City
.
- IP_GEOLOCATION_DB=...
+ MAXMIND_LICENSE_KEY=LNpsJCCKPis6XvBP
+ MAXMIND_EDITION=GeoLite2-City
Note that for the changes in plausible-config.env
to propagate to the plausible
, the container needs to be recreated:
$ docker compose stop plausible
$ docker compose rm plausible
$ docker compose up -d
Also note that using GeoLite2-City
edition requires more RAM than using GeoLite2-Country
.
Now you can remove any other volumes and services used to download, store, and update geolocation databases.
Following changes have been made since v1.5:
with_imported=true
in Stats API aggregate endpointtagged-events
classnamesBamboo.MailgunAdapter
, Bamboo.MandrillAdapter
, Bamboo.SendGridAdapter
plausible/analytics#2649PUT /api/v1/sites
)LOG_FAILED_LOGIN_ATTEMPTS
environment variable to enable failed login attempts logs plausible/analytics#2936MAILER_NAME
environment variable support plausible/analytics#2937MAILGUN_BASE_URI
support for Bamboo.MailgunAdapter
plausible/analytics#2935bounce_rate
IP_BLOCKLIST
environment variablecustom_dimension_filter
feature flag plausible/analytics#2996Published by ruslandoga over 1 year ago
The highlights of this release are:
⚠️ ⚠️ ⚠️
Upgrading to
v2.0
requires performing a data migration.
Please read these notes until the end before deployingv2.0.0-rc.1
The steps below have been tested with clickhouse/clickhouse-server:22.6-alpine
please make sure to upgrade ClickHouse to at least this version.
In your docker-compose.yml update the image used for plausible_events_db to a newer ClickHouse version:
plausible_events_db:
- image: yandex/clickhouse-server:21.3.2.5
+ image: clickhouse/clickhouse-server:22.6-alpine
$ docker compose stop plausible plausible_events_db
$ docker compose rm plausible_events_db
$ docker compose up -d
This will boot up the new version of ClickHouse.
Related PR: https://github.com/plausible/hosting/pull/45
In your docker-compose.yml
update the image used for plausible
to v2.0.0-rc.1
plausible:
- image: plausible/analytics:v1.5.1
+ image: plausible/analytics:v2.0.0-rc.1
and restart the container
$ cd hosting
$ docker compose stop plausible
$ docker compose rm plausible
$ docker compose up -d
This will boot up the new version of the app.
If you open the dashboards now, you wouldn't see any past metrics. This is expected as v2.0
uses the new events_v2
and sessions_v2
tables to store analytics data. We need to perform data migration to copy the data into the new tables.
⚠️ ⚠️ ⚠️
You need enough free disk space available for x2 of the current
plausible_events_db
'sevent-data
volume size. You can use something likedocker system df -v | grep hosting_event-data
to check how much space the current volume is occupying.
Connect to the running plausible
container and start the migration flow
$ cd hosting
$ docker compose exec plausible bin/plausible rpc Plausible.DataMigration.NumericIDs.run
You can attempt this migration multiple times unless you drop v1
tables.
Once you verify the migration went well, the old tables can be dropped. It's easiest to use clickhouse-client
for this
$ ch hosting
$ docker compose exec plausible_events_db clickhouse-client
:) \c plausible_events_db
:) show tables;
:) drop table events;
:) drop table sessions;
See https://clickhouse.com/docs/en/operations/server-configuration-parameters/settings#max-table-size-to-drop for how to drop tables with more than 50GB of data.
In your plausible-config.env
set MAXMIND_LICENSE_KEY
environment variable and get an automatically updated GeoLite2 City geolocation database. The database edition is configurable with MAXMIND_EDITION
environment variable and defaults to GeoLite2-City
.
- IP_GEOLOCATION_DB=...
+ MAXMIND_LICENSE_KEY=LNpsJCCKPis6XvBP
+ MAXMIND_EDITION=GeoLite2-City
Note that for the changes in plausible-config.env
to propagate to the plausible
, the container needs to be recreated:
$ docker compose stop plausible
$ docker compose rm plausible
$ docker compose up -d
Also note that using GeoLite2-City
edition requires more RAM than using GeoLite2-Country
.
Now you can remove any other volumes and services used to download, store, and update geolocation databases.
Following changes have been made since v1.5:
with_imported=true
in Stats API aggregate endpointtagged-events
classnamesBamboo.MailgunAdapter
, Bamboo.MandrillAdapter
, Bamboo.SendGridAdapter
plausible/analytics#2649PUT /api/v1/sites
)LOG_FAILED_LOGIN_ATTEMPTS
environment variable to enable failed login attempts logs plausible/analytics#2936MAILER_NAME
environment variable support plausible/analytics#2937MAILGUN_BASE_URI
support for Bamboo.MailgunAdapter
plausible/analytics#2935bounce_rate
IP_BLOCKLIST
environment variablePublished by ruslandoga over 1 year ago
The highlights of this release are:
⚠️ ⚠️ ⚠️
Upgrading to
v2.0
requires performing a data migration.
Please read these notes until the end before deployingv2.0.0-rc.0
The steps below have been tested with clickhouse/clickhouse-server:22.6-alpine
please make sure to upgrade ClickHouse to at least this version.
In your docker-compose.yml update the image used for plausible_events_db to a newer ClickHouse version:
plausible_events_db:
- image: yandex/clickhouse-server:21.3.2.5
+ image: clickhouse/clickhouse-server:22.6-alpine
$ docker compose stop plausible plausible_events_db
$ docker compose rm plausible_events_db
$ docker compose up -d
This will boot up the new version of ClickHouse.
Related PR: https://github.com/plausible/hosting/pull/45
In your docker-compose.yml
update the image used for plausible
to v2.0.0-rc.0
plausible:
- image: plausible/analytics:v1.5.1
+ image: plausible/analytics:v2.0.0-rc.0
and restart the container
$ cd hosting
$ docker compose stop plausible
$ docker compose rm plausible
$ docker compose up -d
This will boot up the new version of the app.
If you open the dashboards now, you wouldn't see any past metrics. This is expected as v2.0
uses the new events_v2
and sessions_v2
tables to store analytics data. We need to perform data migration to copy the data into the new tables.
⚠️ ⚠️ ⚠️
You need enough free disk space available for x2 of the current
plausible_events_db
'sevent-data
volume size. You can use something likedocker system df -v | grep hosting_event-data
to check how much space the current volume is occupying.
Connect to the running plausible
container and start the migration flow
$ cd hosting
$ docker compose exec plausible bin/plausible rpc Plausible.DataMigration.NumericIDs.run
You can attempt this migration multiple times unless you drop v1
tables.
Once you verify the migration went well, the old tables can be dropped. It's easiest to use clickhouse-client
for this
$ ch hosting
$ docker compose exec plausible_events_db clickhouse-client
:) \c plausible_events_db
:) show tables;
:) drop table events;
:) drop table sessions;
See https://clickhouse.com/docs/en/operations/server-configuration-parameters/settings#max-table-size-to-drop for how to drop tables with more than 50GB of data.
In your plausible-config.env
set MAXMIND_LICENSE_KEY
environment variable and get an automatically updated GeoLite2 City geolocation database. The database edition is configurable with MAXMIND_EDITION
environment variable and defaults to GeoLite2-City
.
- IP_GEOLOCATION_DB=...
+ MAXMIND_LICENSE_KEY=LNpsJCCKPis6XvBP
+ MAXMIND_EDITION=GeoLite2-City
Note that for the changes in plausible-config.env
to propagate to the plausible
, the container needs to be recreated:
$ docker compose stop plausible
$ docker compose rm plausible
$ docker compose up -d
Also note that using GeoLite2-City
edition requires more RAM than using GeoLite2-Country
.
Now you can remove any other volumes and services used to download, store, and update geolocation databases.
Following changes have been made since v1.5:
tagged-events
classnamesBamboo.MailgunAdapter
, Bamboo.MandrillAdapter
, Bamboo.SendGridAdapter
plausible/analytics#2649PUT /api/v1/sites
)bounce_rate
IP_BLOCKLIST
environment variableAdmin user registration is now done through the UI instead of configuration variables. At first launch, users are presented with a registration page which will create the admin account. Admin account related configuration variables are ignored going forward. See below for details.
Admin user registration is required from 1.5.0 onwards. We are deprecating the DISABLE_AUTH
option which allowed Plausible to be used without any user account at all.
Users with existing admin accounts are not affected, but we recommend removing the unused configuration variables. A benefit of moving admin account management to the UI is that you can now change the admin email account through the UI. Previously, this was done by manual database changes and configuration change which required restarting the service.
For v1.5.0-rc.0
changes and upgrade steps please see the previous release candidate discussion.
In your docker-compose.yml
update the image used for plausible
to tag v1.5.0-rc.1
:
plausible:
- image: plausible/analytics:1.5.0-rc.0
+ image: plausible/analytics:v1.5.0-rc.1
$ docker compose stop plausible
$ docker compose rm plausible
$ docker compose up -d
This will boot up the new version of the app.
ADMIN_USER_EMAIL
, ADMIN_USER_NAME
, ADMIN_USER_PWD
, DISABLE_AUTH
environment variables are no longer supported and are ignored if set.
Please remove them from plausible-conf.env
:
- ADMIN_USER_EMAIL=replace-me
- ADMIN_USER_NAME=replace-me
- ADMIN_USER_PWD=replace-me
- DISABLE_AUTH=true
BASE_URL=replace-me
SECRET_KEY_BASE=replace-me
/entrypoint.sh db init-admin
command that was responsible for creating the admin user is also deprecated.
Please remove it from docker-compose.yml
:
plausible:
image: plausible/analytics:v1.5.0-rc.1
- command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh db init-admin && /entrypoint.sh run"
+ command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh run"
Following changes have been made since v1.5.0-rc.0
:
DISABLE_AUTH
is no longer supportedPublished by ruslandoga about 2 years ago
The highlights of this release are:
In your docker-compose.yml
update the image used for plausible
to tag 1.5.0-rc.0
:
plausible:
- image: plausible/analytics:v1.4
+ image: plausible/analytics:1.5.0-rc.0
$ docker compose stop plausible
$ docker compose rm plausible
$ docker compose up -d
This will boot up the new version of the app.
In your docker-compose.yml
, update the image used for plausible_events_db
to the newest stable ClickHouse version:
plausible_events_db:
- image: yandex/clickhouse-server:21.3.2.5
+ image: clickhouse/clickhouse-server:22.6-alpine
$ docker compose stop plausible plausible_events_db
$ docker compose rm plausible_events_db
$ docker compose up -d
This will boot up the new version of ClickHouse.
Related PR: https://github.com/plausible/hosting/pull/45
Upgrading PostgreSQL is a bit trickier, here's the upgrade guide.
Following changes have been made since v1.4:
|
characters with \
in Stats API filter valueslimit
parameter in Stats APIexclusions
script extension now also takes a data-include
attribute tagfile-downloads
script extension for automatically tracking file downloads as custom eventsPUT /api/v1/sites/goals
with form params site_id
, event_name
and/or page_path
, and goal_type
with supported types event
and page
DELETE /api/v1/sites/goals/:goal_id
with form params site_id
u
option can now be used in the manual
extension to specify a URL when triggering events.utm_content
and utm_term
plausible/analytics#515LISTEN_IP
configuration parameter plausible/analytics#1189property=event:goal
returns custom goal properties (within props
)ECTO_IPV6
)contains
, available for page
, entry_page
, exit_page
GET /api/v1/sites/:site_id
script.exclusions.hash.js
.pages.csv
file now includes pageviews again plausible/analytics#1878
script.file-downloads.outbound-links.js
only sends an outbound link event when an outbound download link is clickedentry_page
and exit_page
to be part of the Page
filter groupView all
link to the site-switcher dropdown in the dashboard.+ Add Site
link to the site-switcher dropdown in the dashboard.DISABLE_REGISTRATIONS
configuration parameter can now accept invite_only
to allow invited users to register an account while keeping regular registrations disabled plausible/analytics#1841Published by ukutaht over 2 years ago
Security patch for password reset emails. Analysis of the issue and its impact: https://my-devbox.de/en/blog/accidental-pen-tester-evening/
Published by ukutaht almost 3 years ago
Fixed
Published by ukutaht almost 3 years ago
Published by ukutaht almost 3 years ago
Published by ukutaht almost 3 years ago
The highlights of this release are:
ENABLE_EMAIL_VERIFICATION=true
option.To update your installation, make sure your _docker-compose.yml_l file is referencing plausible/analytics
with the following tag: v1.4.0
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This will run your database migrations and boot up the new version of the app. Following changes have been made since v1.3:
metrics
for the /api/v1/stats/timeseries
endpoint plausible/analytics#952DATABASE_SOCKET_DIR
& DATABASE_NAME
were added.CLICKHOUSE_FLUSH_INTERVAL_MS
and CLICKHOUSE_MAX_BUFFER_SIZE
configuration parameters plausible/analytics#1073path
component of BASE_URL to allow subfolder installatonsENABLE_EMAIL_VERIFICATION=true
if you want to keep the old behaviourPublished by ukutaht about 3 years ago
The highlights of this release are:
ENABLE_EMAIL_VERIFICATION=true
option.This is a release candidate for testing. To update your installation, make sure your docker-compose.yml file is referencing plausible/analytics
with the following tag: v1.4.0-rc.0
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This will run your database migrations and boot up the new version of the app. Following changes have been made since v1.3:
metrics
for the /api/v1/stats/timeseries
endpoint plausible/analytics#952DATABASE_SOCKET_DIR
& DATABASE_NAME
were added.CLICKHOUSE_FLUSH_INTERVAL_MS
and CLICKHOUSE_MAX_BUFFER_SIZE
configuration parameters plausible/analytics#1073path
component of BASE_URL to allow subfolder installatonsENABLE_EMAIL_VERIFICATION=true
if you want to keep the old behaviourPublished by ukutaht over 3 years ago
The highlights of this release are:
maxmindinc/geoipupdate
container is no longer necessary for geolocationThis release bumps the minimum Clickhouse version is 20.8.7.15
so make sure you upgrade your Clickhouse installation if needed.
To update your Plausible installation, make sure your docker-compose.yml file is referencing plausible/analytics
with one of the following tags: latest
, v1
, v1.3
, v1.3.0
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This will run your database migrations and boot up the new version of the app. Following changes have been made since v1.2:
T
and S
, respectively) plausible/analytics#709Published by ukutaht over 3 years ago
The highlights of this release are:
This is a release candidate for testing. To update your installation, make sure your docker-compose.yml file is referencing plausible/analytics
with the following tag: v1.3.0-rc.0
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This will run your database migrations and boot up the new version of the app. Following changes have been made since v1.2:
T
and S
, respectively) plausible/analytics#709Published by ukutaht over 3 years ago
To update your installation, make sure your docker-compose.yml file is referencing plausible/analytics
with one of the following tags: latest
, v1
, v1.2
, v1.2.0
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This will run your database migrations and boot up the new version of the app. Following changes have been made since v1.1:
Published by ukutaht almost 4 years ago
A quick patch release to fix deleting sites that have a spike notification configured. To update your installation, change your docker-compose.yml
file to reference plausible/analytics:v1.2-rc.1
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
Previous release candidate: https://github.com/plausible/analytics/releases/tag/v1.2-rc.0
Published by ukutaht almost 4 years ago
🚧 This is a release candidate for testing purposes. If you decide to give it a try, please leave a message of how it went on the forum
To update your installation, change your docker-compose.yml
file to reference plausible/analytics:v1.2
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This should run your database migrations and boot up the new version of the app. Following changes have been made since v1.1.1
:
Published by ukutaht about 4 years ago